From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: sending changesets from the middle of a git tree
Date: Sun, 14 Aug 2005 11:27:57 +0200 [thread overview]
Message-ID: <20050814092757.GP5608@pasky.ji.cz> (raw)
In-Reply-To: <7vhddtdk86.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Sun, Aug 14, 2005 at 09:57:13AM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> Linus Torvalds <torvalds@osdl.org> writes:
> > Alternatively, use "git cherry", which helps re-order the commits in your
> > tree. They'll be _new_ commits, but they'll have the contents moved over.
>
> > Junio, maybe you want to talk about how you move patches from your "pu"
> > branch to the real branches.
>
> As I have mentioned elsewhere, I have been trying not to use
> JIT, my own Porcelain, to make sure that the core-git barebone
> Porcelain is usable.
>
> Unfortunately, this is one area in my workflow that I still
> heavily rely on JIT, because it is so handy. I've kept saying I
> do not do Porcelain, but I'll make an exception this time, by
> invitation ;-).
Actually, wouldn't this be also precisely for what StGIT is intended to?
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone. -- Alan Cox
next prev parent reply other threads:[~2005-08-14 9:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 3:35 sending changesets from the middle of a git tree Steve French
2005-08-14 4:02 ` 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 [this message]
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=20050814092757.GP5608@pasky.ji.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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).