Re: [fossil-users] Getting a list of what's changed since the last release

2014-07-18 Thread Stephan Beal
On Fri, Jul 18, 2014 at 8:39 PM, Warren Young war...@etr-usa.com wrote:

 When I am assembling a new software release, I assemble a ChangeLog from
 the checkin comments since the last release.  Prior to moving to Fossil, I
 used svn log -r12345:HEAD for this.  That lists the checkin comments from
 r12345 to the current version, only for files in the current directory and
 below, and only on the current branch.


Here's how we do it for fossil releases:

http://www.fossil-scm.org/fossil/vdiff?from=releaseto=trunkdetail=1

where 'release' is a tag which gets places on the most recent release. You
would need, for branch-side work, to put the proper branch name there, but
i think it should just work if you do that.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do. -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Getting a list of what's changed since the last release

2014-07-18 Thread Richard Hipp
On Fri, Jul 18, 2014 at 2:39 PM, Warren Young war...@etr-usa.com wrote:

 When I am assembling a new software release, I assemble a ChangeLog from
 the checkin comments since the last release.


On SQLite and on Fossil I do this:

http://www.sqlite.org/src/timeline?a=releaset=trunkn=1000
http://www.fossil-scm.org/index.html/timeline?a=releaset=trunkn=1000

The above assumes (1) the previous release is labeled with a tag release
and (2) the branch of interest is trunk and (3) there have been fewer than
1000 check-ins on trunk since the previous release.  Make adjustments as
necessary.




  Prior to moving to Fossil, I used svn log -r12345:HEAD for this.  That
 lists the checkin comments from r12345 to the current version, only for
 files in the current directory and below, and only on the current branch.

 The closest I've come to that so far with Fossil is:

 $ fossil timeline after 462b6b3bc5 -n 0

 The artifact ID is that of the last checkin on this branch before the
 ChangeLog was updated for the *previous* release.  So, this tells me what
 happened between that release and now.

 The problem is, it includes all changes in the repository, not just those
 for the current branch.  Ideally, I'd want to restrict it to the current
 subtree, too, as svn does.

 I notice that the Branches tab of fossil ui is able to get a timeline for
 a specific branch, somehow.  I want to get it from the command line because
 I actually do this from within vi:

:r !fossil timeline ... etc

 That is, the output of fossil timeline gets put into the editor at the
 current position.  This turns the ChangeLog assembly task into an editing
 task, rather than a transcription task.
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Getting a list of what's changed since the last release

2014-07-18 Thread Stephan Beal
On Fri, Jul 18, 2014 at 8:43 PM, Stephan Beal sgb...@googlemail.com wrote:

 Here's how we do it for fossil releases:

 http://www.fossil-scm.org/fossil/vdiff?from=releaseto=trunkdetail=1


Correction: that's the diff for that range. Richard's solution gives you
the commit comments.


-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do. -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Getting a list of what's changed since the last release

2014-07-18 Thread Ron W
On Fri, Jul 18, 2014 at 2:39 PM, Warren Young war...@etr-usa.com wrote:

 When I am assembling a new software release, I assemble a ChangeLog from
 the checkin comments since the last release.  Prior to moving to Fossil, I
 used svn log -r12345:HEAD for this.  That lists the checkin comments from
 r12345 to the current version, only for files in the current directory and
 below, and only on the current branch.

 The closest I've come to that so far with Fossil is:

 $ fossil timeline after 462b6b3bc5 -n 0


Try something like:

fossil timeline after  | perl -n -e print if /tags: .*branchname/;

(Also possible to use awk or sed instead of perl)
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Getting a list of what's changed since the last release

2014-07-18 Thread Warren Young

On 7/18/2014 13:05, Ron W wrote:


fossil timeline after  | perl -n -e print if /tags: .*branchname/;


That only works if your commit messages are so short they don't cause a 
line wrap.  I use an 80 column terminal window (old timer, me) so it 
doesn't take much to cause a wrap.  I tried hacking the COLUMNS 
variable, but that doesn't seem to fool Fossil.



(Also possible to use awk or sed instead of perl)


Actually, it looks like you've reinvented grep.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Getting a list of what's changed since the last release

2014-07-18 Thread Warren Young

On 7/18/2014 12:44, Richard Hipp wrote:


http://www.sqlite.org/src/timeline?a=releaset=trunkn=1000


I think clicking the branch from fossil ui then appending a=AFTERSPEC 
will work for me:


http://server:port/repo/timeline?r=BRANCHNAMEa=AFTERSPEC

Today I also learned you can say fossil help /timeline.  I didn't 
expect the HTTP API to be documented.  Neat.


It would be better if I could do this from the command line, though, so 
I could pour the text straight into the text editor.  Just something for 
the project wish list.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Getting a list of what's changed since the last release

2014-07-18 Thread Ron W
On Fri, Jul 18, 2014 at 3:34 PM, Warren Young war...@etr-usa.com wrote:

 On 7/18/2014 13:05, Ron W wrote:


 fossil timeline after  | perl -n -e print if /tags: .*branchname/;


 That only works if your commit messages are so short they don't cause a
 line wrap.  I use an 80 column terminal window (old timer, me) so it
 doesn't take much to cause a wrap.  I tried hacking the COLUMNS variable,
 but that doesn't seem to fool Fossil.


I would have thought Fossil would only wrap lines when STDOUT is a terminal.

We actually append our comments to the relevant ticket, so our commit
message are just the ticket ID. Each comment appended includes the commit
ID. (Maybe we should duplicate the comments in the commits, but we don't)




  (Also possible to use awk or sed instead of perl)


 Actually, it looks like you've reinvented grep.


Forgot about grep. Most of my non-C/C++ coding is in Perl, so I tend to use
that.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Getting a list of what's changed since the last release

2014-07-18 Thread Kees Nuyt
[Default] On Fri, 18 Jul 2014 13:34:26 -0600, Warren Young
war...@etr-usa.com wrote:

On 7/18/2014 13:05, Ron W wrote:

 fossil timeline after  | perl -n -e print if /tags: .*branchname/;

That only works if your commit messages are so short they don't cause a 
line wrap.  I use an 80 column terminal window (old timer, me) so it 
doesn't take much to cause a wrap.  I tried hacking the COLUMNS 
variable, but that doesn't seem to fool Fossil.

That was solved some time ago:

fossil help timeline 
:
  -W|--width num  Width of lines (default is to auto-detect).
Must be 20 or 0 (= no limit, resulting in
a single line per entry).
 
 (Also possible to use awk or sed instead of perl)

Actually, it looks like you've reinvented grep.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

-- 
Groet, Cordialement, Pozdrawiam, Regards,

Kees Nuyt

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users