[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Switching to git
From: |
Ryan Harper |
Subject: |
Re: [Qemu-devel] Switching to git |
Date: |
Wed, 22 Apr 2009 13:13:28 -0500 |
User-agent: |
Mutt/1.5.6+20040907i |
* Andreas F?rber <address@hidden> [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
> >><address@hidden> 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
address@hidden
Re: [Qemu-devel] Switching to git, Johannes Schindelin, 2009/04/22