On Mon, 20 Jun 2011 16:18:09 -0000, Adam Reviczky <email address hidden> wrote:
> > Does {date} do what you need here?
>
> Thanks, yes that will do it.
>
> > Why do you need the form with the dots?
>
> I need it, because it is used as a version string (for a daily build).
>
> see:
> # bzr-builder format 0.3 deb-version 2011.06.20
> lp:~reviczky/context-beta/cont-tmf
> nest-part packaging lp:context-beta debian debian
>
> I'm increasing it manually at the moment.
Hmm, I can see why the dots make a difference there, but I'm struggling
to come up with a case where it would make a useful distinction.
I'm not against having this, but I'm unsure if it should allow a full
format string. At the same time I don't really want {date-with-dots}.
I think that the format string is more palatable of the two.
I wonder if something like {date:with-dots} would be a good compromise.
On Mon, 20 Jun 2011 16:18:09 -0000, Adam Reviczky <email address hidden> wrote:
> > Does {date} do what you need here?
>
> Thanks, yes that will do it.
>
> > Why do you need the form with the dots?
>
> I need it, because it is used as a version string (for a daily build).
>
> see:
> # bzr-builder format 0.3 deb-version 2011.06.20
> lp:~reviczky/context-beta/cont-tmf
> nest-part packaging lp:context-beta debian debian
>
> I'm increasing it manually at the moment.
Hmm, I can see why the dots make a difference there, but I'm struggling
to come up with a case where it would make a useful distinction.
I'm not against having this, but I'm unsure if it should allow a full
format string. At the same time I don't really want {date-with-dots}.
I think that the format string is more palatable of the two.
I wonder if something like {date:with-dots} would be a good compromise.
Thanks,
James