qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Switching to git
Date: Wed, 22 Apr 2009 13:13:28 -0500	[thread overview]
Message-ID: <20090422181328.GF25977@us.ibm.com> (raw)
In-Reply-To: <0240830B-5527-4567-B605-51C173C39239@web.de>

* Andreas F?rber <andreas.faerber@web.de> [2009-04-22 13:03]:
> 
> Am 22.04.2009 um 16:22 schrieb Anthony Liguori:
> 
> >Laurent Desnogues wrote:
> >>On Wed, Apr 22, 2009 at 3:22 PM, Anthony Liguori  
> >><aliguori@us.ibm.com> wrote:
> >>[...]
> >>
> >>>For users, to get the latest QEMU bits, you would do:
> >>>
> >>>$ git clone git://git.savannah.nongnu.org/qemu.git
> >>>
> >>>
> >>>For maintainers, Savannah has a getting started page that  
> >>>describes how to
> >>>push commits at http://savannah.gnu.org/maintenance/UsingGit
> >>>
> >>
> >>And what for people between users and maintainers, for instance those
> >>who propose patches?  Will there be some recommendations on how
> >>to post patches so that it works well?  And don't forget that for  
> >>some
> >>people just telling "a set of patches is good as long as it can be
> >>bisected" is too short :-)
> >>
> >
> >Yup, we'll have a SubmittingPatches that provides the recommended  
> >work flow.  A really nice property of git is that if you use the  
> >various git tools to send patches (git-format-patch/git-send-email)  
> >then a maintainer can grab those automatically via git-am.  It  
> >significantly reduces the likelihood of loosing information in the  
> >process.
> 
> Unfortunately tools like git-send-email make me loose information  
> instead, by not saving the sent patches in my mail client's or IMAP  
> server's Sent Mail folder...

git-send-email sends you a copy of the patches sent.


-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com

  parent reply	other threads:[~2009-04-22 18:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 13:22 [Qemu-devel] Switching to git Anthony Liguori
2009-04-22 13:57 ` Kevin Wolf
2009-04-22 14:05   ` Anthony Liguori
2009-04-22 14:12 ` Gerd Hoffmann
2009-04-22 14:20 ` Laurent Desnogues
2009-04-22 14:22   ` Anthony Liguori
2009-04-22 14:37     ` Avi Kivity
2009-04-22 17:53     ` Andreas Färber
2009-04-22 18:09       ` Jamie Lokier
2009-04-22 18:13       ` Ryan Harper [this message]
2009-04-22 18:48       ` Avi Kivity
2009-04-22 14:38   ` Lennart Sorensen
2009-04-22 14:45     ` Laurent Desnogues
2009-04-22 14:50       ` Lennart Sorensen
2009-04-22 17:25 ` Johannes Schindelin
2009-04-22 17:49   ` Anthony Liguori

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=20090422181328.GF25977@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=andreas.faerber@web.de \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).