git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pascal Obry <pascal@obry.net>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Mike Hommey <mh@glandium.org>, git@vger.kernel.org
Subject: Re: how to create v2 patch
Date: Thu, 06 Dec 2007 22:38:14 +0100	[thread overview]
Message-ID: <47586BC6.2020100@obry.net> (raw)
In-Reply-To: <475855D6.201@imap.cc>

Tilman Schmidt a écrit :
> Hmm. But wouldn't each of these approaches lead to my original
> commit being removed from my git repository? And isn't removing
> commits that have already been published strongly discouraged?

They won't be removed, just changed/merged... and that's what you were
looking for or I did not understand your question! This is not bad
practice as it is done on YOUR repository. Of course this should never
be done on a pushed/published changeset.

Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|              http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595

  parent reply	other threads:[~2007-12-06 21:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-01 12:41 how to create v2 patch Tilman Schmidt
2007-12-01 13:17 ` Pascal Obry
2007-12-01 13:43   ` Mike Hommey
2007-12-06 20:04     ` Tilman Schmidt
2007-12-06 20:44       ` Jan Hudec
2007-12-06 21:38       ` Pascal Obry [this message]
2007-12-06 22:03       ` Andreas Ericsson
2007-12-07  8:11       ` Wincent Colaiuta
2007-12-01 14:02 ` Jakub Narebski
2007-12-01 14:14   ` Björn Steinbrink

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=47586BC6.2020100@obry.net \
    --to=pascal@obry.net \
    --cc=git@vger.kernel.org \
    --cc=mh@glandium.org \
    --cc=tilman@imap.cc \
    /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).