All of lore.kernel.org
 help / color / mirror / Atom feed
From: Noel Grandin <noel@peralex.com>
To: Petr Baudis <pasky@ucw.cz>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 1/3] Introduce "rev-list --stop-at=<commit>".
Date: Fri, 13 May 2005 08:07:15 +0200	[thread overview]
Message-ID: <42844413.5020004@peralex.com> (raw)
In-Reply-To: <20050513052901.GB16464@pasky.ji.cz>

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

Also, it should be called --stop-before given it's behaviour.
--stop-at implies that it includes the given commit.

Petr Baudis wrote:

>Dear diary, on Fri, May 13, 2005 at 02:15:15AM CEST, I got a letter
>where Junio C Hamano <junkio@cox.net> told me that...
>  
>
>>Additional option, --stop-at=<commit>, is introduced.  The
>>git-rev-list output stops just before showing the named commit.
>>
>>This is based on Thoms Gleixner's patch but slightly reworked.
>>
>>Signed-off-by: Junio C Hamano <junkio@cox.net>
>>    
>>
>
>Won't apply for now - as I already said in the relevant thread, this
>makes no sense with the current git-rev-list output order, and even
>encourages using it in wrong way. It is ok when the merges are reported
>in a different way, but that's impossible without some repoid (I yet
>have to catch up with that thread :-).
>
>  
>


NOTICE: Please note that this email, and the contents thereof, 
are subject to the standard Peralex email disclaimer, which may 
be found at: http://www.peralex.com/disclaimer.html

If you cannot access the disclaimer through the URL attached 
 and you wish to receive a copy thereof please send 
 an email to email@peralex.com

  reply	other threads:[~2005-05-13  6:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13  0:15 [PATCH 1/3] Introduce "rev-list --stop-at=<commit>" Junio C Hamano
2005-05-13  5:29 ` Petr Baudis
2005-05-13  6:07   ` Noel Grandin [this message]
2005-05-13  7:36   ` Junio C Hamano

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=42844413.5020004@peralex.com \
    --to=noel@peralex.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=pasky@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.