From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lz6Xv-0000uJ-IV for qemu-devel@nongnu.org; Wed, 29 Apr 2009 05:57:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lz6Xq-0000sO-Hc for qemu-devel@nongnu.org; Wed, 29 Apr 2009 05:57:42 -0400 Received: from [199.232.76.173] (port=55041 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lz6Xq-0000sL-9o for qemu-devel@nongnu.org; Wed, 29 Apr 2009 05:57:38 -0400 Received: from smtp5-g21.free.fr ([212.27.42.5]:47791) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lz6Xp-0007Kj-80 for qemu-devel@nongnu.org; Wed, 29 Apr 2009 05:57:37 -0400 In-Reply-To: <87r5zberwc.fsf@pike.pond.sub.org> Subject: Re: [Qemu-devel] updating git tree From: "=?utf-8?q?Fran=C3=A7ois?= Revol" Date: Wed, 29 Apr 2009 11:57:50 +0200 CEST Message-Id: <6474615666-BeMail@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: andreas.faerber@web.de, qemu-devel@nongnu.org > > This sounds confuse... > > anyway. > > The index can be confusing for beginners. Just think about it as > your > commit staging area. Having a staging area lets me construct what I > want to commit incrementally. I find that especially useful when my > working tree is in a messy state. Sure, likely works much better than grepping svn stat to split stuff, or echo "svn ci foo bar/plop -m 'some commit'" >> pending.txt once you spent the time you didn't have to learn it of course. > Try git-add -p some time, and you'll understand. Hmm not documented here, git too old again I guess. > > There is no reason it would make me a mail in any format that I > > don't > > use. > > mbox is not standard, despite it storing messages themselves in RFC > > format. > > I'm not sure I understand what you're talking about. > > git-format-patch puts each commit in a separate file. Mbox comes > into > play only if you use --stdout. Still it outputs a single mbox mail, not a patch... > NAME > git-format-patch - Prepare patches for e-mail submission which is different to me than "prepare patch as e-mail for submission" > > It tries to impose a format on me that I don't want. > > There is no reason I want to setup a mail account on this box while > > I > > have all my mail on another box on another OS in another format > > (almost > > maildir just better). And I don't like having send-mails hiding > > elsewhere. > > Maybe you're looking for git-show. git-show doesn't seem to know about Signed-off-by, so it must still be done by hand anyway... Anyway, sed magic works for me. > I trust venting your frustration is good for you, but I doubt it's > good > for getting help :) Well I'm thankful to you and some other who do try to help, but the first mails after the announce were more like "oh we switched to git and don't care if you don't know it and actually laugh at you, everyone knows git, git is nice, git is all logical, it's you who is weird", at least that's how I felt it. > > No commit since fc1c67bc2a43a53f7315b602e0c67f9604835fe1 =3F > > Hmm oh, no way to do a "git log" on a git: url without a clone =3F > > Sorry, I don't understand what you're trying to do. Something like svn log svn://svn.berlios.de/haiku/haiku/trunk -v | more svn diff svn://svn.berlios.de/haiku/haiku/trunk -r30330:30331 | more which doesn't require a checkout or a web browser; oh well, nevermind. Fran=C3=A7ois.