From: Blaisorblade <blaisorblade@yahoo.it>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Really BAD granularity example in BKCVS output
Date: Tue, 9 Aug 2005 21:20:48 +0200 [thread overview]
Message-ID: <200508092120.48236.blaisorblade@yahoo.it> (raw)
I've locally downloaded and installed the GIT version of the BitKeeper tree
(the first existing upload - have been away for a while, don't know if there
are others), and while browsing the history for some work, I found this
commit:
http://localhost/~paolo/git/?p=old-2.6-bkcvs/.git;a=commit;h=b035f9332ce7e205af43f7cfdf4e1cf3625f7ad5
(the hashes work on the kernel.org copy of that repository, assuming it wasn't
re-exported).
Well, that is *awfully* big (543 files touched)! Isn't there anything which
can be done about that? What is worse, the commit message is truncated!
And yes, sorry if this is a stupid question.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Messenger: chiamate gratuite in tutto il mondo
http://it.beta.messenger.yahoo.com
reply other threads:[~2005-08-12 13:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200508092120.48236.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®