including a checksum of the diff in uname

[Mateusz Guzik]

On Thu, May 17, 2018 at 8:37 AM, Eitan Adler <lists at eitanadler.com> wrote:

> On 12 May 2018 at 19:50, Mateusz Guzik <mjguzik at gmail.com> wrote:
> > On Sun, May 13, 2018 at 4:41 AM, Eitan Adler <lists at eitanadler.com>
> wrote:
> >>
> >> Hi all,
> >>
> >> I often have several variants of the same revision that I'm testing or
> >> working on at any given time.
> >>
> >> What do you y'all think of something like this:
> >>
> >> Index: sys/conf/newvers.sh
> >> ===================================================================
> >> --- sys/conf/newvers.sh (revision 333575)
> >> +++ sys/conf/newvers.sh (working copy)
> >> @@ -203,6 +203,8 @@ if [ -n "$svnversion" ] ; then
> >>   [0-9]*[MSP]|*:*)
> >>   svn=" r${svn}"
> >>   modified=true
> >> + ck="$(svn diff | cksum | cut -w -f 1)"
> >> + svn="$svn-$ck"
> >>   ;;
> >>   [0-9]*)
> >>   svn=" r${svn}"
> >>
> >> to help differentiate.
> >>
> >> You end up with a version that looks like: r333575M-4294967295?
> >>
> >
> > Don't develop with svn. get yourself a git or hg setup and a tmp branch.
> > The branch name is always included along with the commit hash.
>
> That makes sense, and I might do that in the future. In the past
> adding files was more painful with git, though I'm told this is no
> longer the case.
>
> In any case, is there any reason not to add the above patch?
>
>
I don't see any added value of doing so. So far it just looks like
patching up a deficient development process.

-- 
Mateusz Guzik <mjguzik gmail.com>