On Sun, Jul 26, 2015 at 5:39 PM, Duy Nguyen <pclo...@gmail.com> wrote:
> On Sun, Jul 26, 2015 at 11:08 AM, Eric Sunshine <sunsh...@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".
> --
> Duy
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
You can normally find the previous commit via the reflog. Various
changes to the settings can make the reflog be maintained for longer
if you have longer lived patch series. That's how I would suggest it,
rather than branches, as I tend not to keep old versions around on
separate tags or branches.
The problem with "foo@{/v2}" is that people don't always keep values
inside the message it self, but maybe "foo@{/pattern}" would be a
useful extension?
Regards,
Jake
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
