On Mon, Jul 27, 2015 at 2:39 PM, Jacob Keller <jacob.kel...@gmail.com> wrote:
> 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".
>
> 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?
"reflog message" is different from "commit message". I was referring
to the first one (which is out of user control), perhaps you were
referring to the second one? I don't expect people to add v2 to
manually. If we have something like foo@{/v2} then we can teach
send-email (or format-patch) to add a reflog entry with "v2" in it.
But maybe we're abusing reflog..
--
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
