git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Duy Nguyen <pclouds@gmail.com>
To: Jacob Keller <jacob.keller@gmail.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
	Karthik Nayak <karthik.188@gmail.com>,
	Git List <git@vger.kernel.org>,
	Christian Couder <christian.couder@gmail.com>,
	Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v4 01/10] ref-filter: add option to align atoms to the left
Date: Tue, 28 Jul 2015 17:35:44 +0700	[thread overview]
Message-ID: <CACsJy8DMAUfOPHRZuOhf1dLABqhb_aP3LOLqBE7xo3_aMMSyYg@mail.gmail.com> (raw)
In-Reply-To: <CACsJy8Dr29B7Lei-jFqgPViZwd6BZcJde0jkcAwySYcY2v8QqA@mail.gmail.com>

On Mon, Jul 27, 2015 at 5:18 PM, Duy Nguyen <pclouds@gmail.com> wrote:
> On Mon, Jul 27, 2015 at 2:39 PM, Jacob Keller <jacob.keller@gmail.com> wrote:
>> On Sun, Jul 26, 2015 at 5:39 PM, Duy Nguyen <pclouds@gmail.com> wrote:
>>> On Sun, Jul 26, 2015 at 11:08 AM, Eric Sunshine <sunshine@sunshineco.com> wrote:
>>>> You can generate an interdiff with "git diff branchname-v4
>>>> branchname-v5", for instance.
>>>
>>> Off topic. But what stops me from doing this often is it creates a big
>>> mess in "git tag -l". Do we have an option to hide away some
>>> "insignificant:" tags? reflog might be an option if we have something
>>> like foo@{/v2} to quickly retrieve the reflog entry whose message
>>> contains "v2".
> ...
>
> But maybe we're abusing reflog..

Actually a good place for this stuff is "git branch
--edit-description". A lot of manual steps to save old refs, do
inter-diff.. but it's probably good enough.
-- 
Duy

  reply	other threads:[~2015-07-28 10:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 19:04 [PATCH v4 0/10] port tag.c to use ref-filter APIs Karthik Nayak
2015-07-24 19:04 ` [PATCH v4 01/10] ref-filter: add option to align atoms to the left Karthik Nayak
2015-07-24 21:54   ` Junio C Hamano
2015-07-24 23:00     ` Junio C Hamano
2015-07-25  4:14       ` Karthik Nayak
2015-07-26  4:08   ` Eric Sunshine
2015-07-26  4:36     ` Karthik Nayak
2015-07-26  5:58       ` Eric Sunshine
2015-07-26  6:03         ` Karthik Nayak
2015-07-27 12:01       ` Matthieu Moy
2015-07-27  0:39     ` Duy Nguyen
2015-07-27  7:39       ` Jacob Keller
2015-07-27 10:18         ` Duy Nguyen
2015-07-28 10:35           ` Duy Nguyen [this message]
2015-07-24 19:04 ` [PATCH v4 02/10] ref-filter: make the 'color' use ref_formatting_state Karthik Nayak
2015-07-24 21:46   ` Junio C Hamano
2015-07-25  4:15     ` Karthik Nayak
2015-07-26  4:28       ` Eric Sunshine
2015-07-26  4:12   ` Eric Sunshine
2015-07-26  5:40     ` Karthik Nayak
2015-07-24 19:04 ` [PATCH v4 03/10] ref-filter: add option to filter only tags Karthik Nayak
2015-07-24 19:04 ` [PATCH v4 04/10] ref-filter: support printing N lines from tag annotation Karthik Nayak
2015-07-26  4:46   ` Eric Sunshine
2015-07-26  5:15     ` Karthik Nayak
2015-07-24 19:04 ` [PATCH v4 05/10] ref-filter: add support to sort by version Karthik Nayak
2015-07-25 22:40   ` Junio C Hamano
2015-07-26  5:07     ` Karthik Nayak
2015-07-27 15:24       ` Junio C Hamano
2015-07-27 17:03         ` Karthik Nayak
2015-07-24 19:04 ` [PATCH v4 06/10] ref-filter: add option to match literal pattern Karthik Nayak
2015-07-26  5:15   ` Eric Sunshine
2015-07-26 18:21     ` Karthik Nayak
2015-07-24 19:04 ` [PATCH v4 07/10] tag.c: use 'ref-filter' data structures Karthik Nayak
2015-07-24 19:19 ` [PATCH v4 08/10] tag.c: use 'ref-filter' APIs Karthik Nayak
2015-07-24 19:19   ` [PATCH v4 09/10] tag.c: implement '--format' option Karthik Nayak
2015-07-24 19:19   ` [PATCH v4 10/10] tag.c: implement '--merged' and '--no-merged' options Karthik Nayak

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACsJy8DMAUfOPHRZuOhf1dLABqhb_aP3LOLqBE7xo3_aMMSyYg@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jacob.keller@gmail.com \
    --cc=karthik.188@gmail.com \
    --cc=sunshine@sunshineco.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).