git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@austin.rr.com>
To: git@vger.kernel.org
Subject: sending changesets from the middle of a git tree
Date: Sat, 13 Aug 2005 22:35:50 -0500	[thread overview]
Message-ID: <42FEBC16.9050309@austin.rr.com> (raw)

Just to confirm a recent answer to questions on lkml ...

1) There is no way to send a particular changeset from the "middle" of a 
set from one tree to another, without exporting it as a patch or 
rebuilding a new git tree.   I have two changesets that, after testing 
last week, I now consider more important to send upstream than the few 
earlier and later changesets.   If I export those two changesets as 
patches, and send them on. presumably I lose the changset comments etc. 
and then when the upstream tree is merged back, it might look a little 
odd in the changeset history.

2) There is no way to update the comment field of a changeset after it 
goes in (e.g. to add a bugzilla bug number for a bug that was opened 
just after the fix went in).

3) There is no way to do a test commit of an individual changeset 
against a specified tree (to make sure it would still merge cleanly, 
automatically).

Are there easier ways to do any of these?

             reply	other threads:[~2005-08-14  3:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14  3:35 Steve French [this message]
2005-08-14  4:02 ` sending changesets from the middle of a git tree Ryan Anderson
2005-08-15  6:35   ` Ryan Anderson
2005-08-14  5:03 ` Linus Torvalds
2005-08-14  5:16   ` Linus Torvalds
2005-08-14  7:57   ` Junio C Hamano
2005-08-14  9:27     ` Petr Baudis
2005-08-15  1:37       ` Junio C Hamano
2005-08-15  8:55         ` Catalin Marinas
2005-08-17  0:13         ` Wolfgang Denk
2005-08-17  0:55           ` Junio C Hamano
2005-08-15  9:27 ` Catalin Marinas

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=42FEBC16.9050309@austin.rr.com \
    --to=smfrench@austin.rr.com \
    --cc=git@vger.kernel.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).