qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: "François Revol" <revol@free.fr>
Cc: andreas.faerber@web.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] updating git tree
Date: Wed, 29 Apr 2009 11:22:11 +0200	[thread overview]
Message-ID: <87r5zberwc.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <2472635194-BeMail@laptop> ("François Revol"'s message of "Wed\, 29 Apr 2009 10\:51\:08 +0200 CEST")

"François Revol" <revol@free.fr> writes:

> <rant cause="I'm right but you might not have time to read it">
>
>> >> That I guessed, but there is no way to forbid commiting deleted 
>> > > files 
>> >> at once...
>> 
>> There is.
>> 
>> git-commit by default commits exactly what you staged in the index.  
>> If
>> you staged a delete, it'll commit a delete.  If you don't want that,
>> unstage it, say with git-add or git-reset.
>> 
>> git-commit can also bypass the index.  Just list the files you want 
>> to
>> commit.  If a listed file no longer exists, the commit will remove 
>> it.
>
> 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.

Try git-add -p some time, and you'll understand.

>> > (overengineering)
>> 
>> If you want a diff, use git-diff.
>> 
>> If you want e-mail ready for sending, use git-format-patch.
>
> I want a patch ready to submit, that is, a diff with the Signed-off-by 
> tag as it is supposed to be able to do this, and the commit summary as 
> it knows about it.
>
> 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.

> <obvious>
> Besides the command is named git format-*patch* *not* format-mail!
> </obvious>

>From its man page:

NAME
       git-format-patch - Prepare patches for e-mail submission

>> Me thinks you are still fighting the tool instead of working with it.
>> No happiness found down that way.
>
> It's the tool that is fighting me instead of doing what I want it to 
> do.
> 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.

> Why does it think I want to let it send mails for me ? I don't like 
> apps that does things behind my back, that sounds so Windows-ish. :^\
> I thought UNIX philosophy was all about interoperability...
>
> </rant>

I trust venting your frustration is good for you, but I doubt it's good
for getting help :)

> Let's see if it still works today...
>
> No commit since fc1c67bc2a43a53f7315b602e0c67f9604835fe1 ?
> Hmm oh, no way to do a "git log" on a git: url without a clone ?

Sorry, I don't understand what you're trying to do.

> Btw, front page: "The a QEMU repository" typo. It could reuse a link 
> too...
> http://savannah.nongnu.org/git/?group=qemu ?
>
> François.

  reply	other threads:[~2009-04-29  9:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <77A0C157-5334-4505-BDDA-324862C1E429@hotmail.com>
2009-04-28  6:50 ` [Qemu-devel] updating git tree C.W. Betts
2009-04-28  6:54   ` Laurent Desnogues
2009-04-28  7:21     ` Bartlomiej Celary
2009-04-28  8:49     ` Christoph Egger
2009-04-28  9:32       ` Kevin Wolf
2009-04-28  9:38       ` [Qemu-devel] " Jan Kiszka
2009-04-28  9:42         ` Laurent Desnogues
2009-04-28 10:04         ` Kevin Wolf
2009-04-28 10:20           ` Jan Kiszka
2009-04-28 10:28             ` Kevin Wolf
2009-04-28 10:48               ` Jan Kiszka
2009-04-28 10:58                 ` Kevin Wolf
2009-04-28 11:14                   ` Jan Kiszka
2009-04-28 11:15                 ` François Revol
2009-04-28 10:25           ` Gerd Hoffmann
2009-04-28 11:11       ` [Qemu-devel] " François Revol
2009-04-28 12:03         ` Laurent Desnogues
2009-04-28 12:57           ` François Revol
2009-04-28 13:10             ` Laurent Vivier
2009-04-28 13:49               ` François Revol
2009-04-28 13:58                 ` Kevin Wolf
2009-04-28 15:10                   ` Laurent Vivier
2009-04-28 15:22                     ` Kevin Wolf
2009-04-28 15:40                       ` Laurent Vivier
2009-04-28 16:51               ` Andreas Färber
2009-04-28 19:25                 ` François Revol
2009-04-28 19:49                   ` Andreas Färber
2009-04-28 20:17                     ` François Revol
2009-04-28 21:01                       ` François Revol
2009-04-29  7:54                         ` Markus Armbruster
2009-04-29  8:51                           ` François Revol
2009-04-29  9:22                             ` Markus Armbruster [this message]
2009-04-29  9:57                               ` François Revol
2009-04-29  7:44                       ` Markus Armbruster

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=87r5zberwc.fsf@pike.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=andreas.faerber@web.de \
    --cc=qemu-devel@nongnu.org \
    --cc=revol@free.fr \
    /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;
as well as URLs for NNTP newsgroup(s).