Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 Dec 2020 15:20:55 -0700
From:      Alan Somers <asomers@freebsd.org>
To:        Rick Macklem <rmacklem@uoguelph.ca>
Cc:        "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject:   Re: referencing one commit in another for git
Message-ID:  <CAOtMX2gsYVeN1NZVjtGX7EDNFnL2qKV%2Bg3GtSS-YFyn1A6_wLg@mail.gmail.com>
In-Reply-To: <YQXPR0101MB0968535A875FF1D2C32352E8DDDE0@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>
References:  <YQXPR0101MB0968535A875FF1D2C32352E8DDDE0@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 23, 2020 at 3:16 PM Rick Macklem <rmacklem@uoguelph.ca> wrote:

> Hi,
>
> So I just did my first git commit. Pretty scary, but it looks ok.
>
> Now, how do I reference one commit in another related
> commit's log?
>
> By the long winded hash or ??
>
> I'm not sure if I should ask here or on the git mailing list,
> but I figured this isn't a technical git question...
>
> Thanks for any help with this, rick
>

Yeah, you should use the full hash.  For temporary references, like during
a code review, you can use the first "several" digits of the hash.   For a
project of FreeBSD's size, "several" is probably 11-13.  But in permanent
contexts, like commit logs, you should use the full hash.  When somebody
views the commit on a platform like Github, Github will automatically turn
it into a hyperlink, and display only the first "several" digits.
-Alan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2gsYVeN1NZVjtGX7EDNFnL2qKV%2Bg3GtSS-YFyn1A6_wLg>