Git development
 help / color / mirror / Atom feed
From: Francis Galiegue <fg@one2team.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chris Frey <cdfrey@foursquare.net>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Alex Riesen <raa.lkml@gmail.com>,
	Junio C Hamano <gitster@pobox.com>, Miles Bader <miles@gnu.org>,
	git@vger.kernel.org
Subject: Re: multiple-commit cherry-pick?
Date: Fri, 14 Nov 2008 19:38:24 +0100	[thread overview]
Message-ID: <200811141938.24734.fg@one2team.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0811140800540.3468@nehalem.linux-foundation.org>

Le Friday 14 November 2008 17:11:41 Linus Torvalds, vous avez écrit :
[...]
>
> So we _could_ do something like
>
> 	git log {a..b} [...]
>

I don't know if you really meant this, but entering SHA1s as is at a shell 
prompt may have dangerous side effects... If not right now, then in (some not 
so distant time in) the future. Consider this (I use bash 3.2, maintained by 
Gentoo):

$ echo {a..c}
a b c

Who knows if some day they won't have the idea of, say, 
extending "{aeb32ca..ee23ff1}" to, well... You see what I mean.

-- 
Francis Galiegue
ONE2TEAM
Ingénieur système
Mob : +33 (0) 6 83 87 78 75
Tel : +33 (0) 1 78 94 55 52
fge@one2team.com
40 avenue Raymond Poincaré
75116 Paris

  parent reply	other threads:[~2008-11-14 18:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06  2:45 multiple-commit cherry-pick? Miles Bader
2008-11-06  3:24 ` Deskin Miller
2008-11-06  9:51   ` Björn Steinbrink
2008-11-06 12:14     ` Miles Bader
2008-11-06 12:26       ` Björn Steinbrink
2008-11-07  5:09         ` Miles Bader
2008-11-07 11:03           ` Björn Steinbrink
2008-11-07 11:46             ` Miles Bader
2008-11-06 21:37 ` Alex Riesen
2008-11-07  3:29   ` Linus Torvalds
2008-11-07  4:38     ` Miles Bader
2008-11-07  7:13       ` Alex Riesen
2008-11-07  5:00     ` Junio C Hamano
2008-11-07  7:12       ` Alex Riesen
2008-11-07 18:08         ` Linus Torvalds
2008-11-09 10:25           ` Alex Riesen
2008-11-10 19:58             ` Johannes Schindelin
2008-11-10 20:24               ` Alex Riesen
2008-11-10 21:31                 ` Johannes Schindelin
2008-11-14  5:08                   ` Chris Frey
2008-11-14 14:00                     ` Johannes Schindelin
2008-11-14 16:11                     ` Linus Torvalds
2008-11-14 16:59                       ` Johannes Schindelin
2008-11-14 17:29                       ` Junio C Hamano
2008-11-14 17:41                         ` Linus Torvalds
2008-11-14 17:55                           ` Linus Torvalds
2008-11-16  9:11                             ` Pierre Habouzit
2008-11-14 18:38                       ` Francis Galiegue [this message]
2008-11-10 20:41               ` Junio C Hamano
2008-11-10 21:34                 ` Johannes Schindelin
2008-11-07 10:46       ` Michael Radziej

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=200811141938.24734.fg@one2team.com \
    --to=fg@one2team.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=cdfrey@foursquare.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=miles@gnu.org \
    --cc=raa.lkml@gmail.com \
    --cc=torvalds@linux-foundation.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