From: Petr Baudis <hidden> Date: 2005-12-12 01:12:13
Hello,
this is Cogito version 0.16.1, the next stable release of the
human-friendly version control UI for the Linus' GIT tool. Share
and enjoy at:
http://www.kernel.org/pub/software/scm/cogito/
This crispy new release gives you a few minor to medium bugfixes and
a significant cg-patch speedup. You can reach it as the "v0.16" branch
of the Cogito repository. Note that this is just the stable branch, more
interesting stuff is happenning (and especially going to happen) on the
master development branch; if everything goes well, I might release
cogito-0.17rc1 at the end of this week).
So the new stuff since 0.16 is:
Jonas Fonseca:
cg-merge: Improve the hook description
cg-status: handle subdirs when listing heads
Petr Baudis:
Fix cg-admin-setuprepo warning on missing post-update hook
Initial cg-push to a remote branch wouldn't work properly
Fix cg-object-id <singleletter>
Fix unsafe sed usage in scripts
cg-clean -n will just pretend to remove stuff
Make cg-clean whitespace-safe
If you use filenames with spaces _and_ cg-clean (or cg-clean
at all, after all), you should certainly upgrade!
bash-3.1-related fixes
Fix broken cg-log FILE in subdirectory
Drastically speed up cg-patch
cogito-0.16.1
Happy hacking,
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
From: Petr Baudis <hidden> Date: 2016-06-15 22:42:14
Dear diary, on Mon, Dec 12, 2005 at 02:12:10AM CET, I got a letter
where Petr Baudis [off-list ref] said that...
this is Cogito version 0.16.1, the next stable release of the
human-friendly version control UI for the Linus' GIT tool.
By the way, did anyone receive the 0.16 announcement? I have it in my
=sent mailbox, but not in either the git@ or linux-kernel@ mailboxes...
*perplexed*
Thanks,
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
On Mon, 12 Dec 2005 02:14:11 +0100
Petr Baudis wrote:
By the way, did anyone receive the 0.16 announcement? I have it in my
=sent mailbox, but not in either the git@ or linux-kernel@ mailboxes...
*perplexed*
I see the 0.16 RC1 and RC2 mails, but not the 0.16 announcement. When didn't
you send it?
From: Paul Dickson <hidden> Date: 2016-06-15 22:42:14
On Mon, 12 Dec 2005 02:12:10 +0100, Petr Baudis wrote:
this is Cogito version 0.16.1, the next stable release of the
human-friendly version control UI for the Linus' GIT tool.
The help from cg-admin-setuprepo say it will create the repo in the given
directory, but doesn't say it must create the directory.
$ mkdir ~/test
$ cg-admin-setuprepo ~/test
cg-admin-setuprepo: /home/dickson/test already exists
There seems to be a missing step in the help instructions:
$ cg-admin-setuprepo ~/test/test1
$ cg-push
cg-push: where to push to?
-Paul
From: Petr Baudis <hidden> Date: 2016-06-15 22:42:14
Dear diary, on Tue, Dec 13, 2005 at 02:02:15AM CET, I got a letter
where Paul Dickson [off-list ref] said that...
On Mon, 12 Dec 2005 02:12:10 +0100, Petr Baudis wrote:
quoted
this is Cogito version 0.16.1, the next stable release of the
human-friendly version control UI for the Linus' GIT tool.
The help from cg-admin-setuprepo say it will create the repo in the given
directory, but doesn't say it must create the directory.
$ mkdir ~/test
$ cg-admin-setuprepo ~/test
cg-admin-setuprepo: /home/dickson/test already exists
Good point. I've added it to the description.
There seems to be a missing step in the help instructions:
$ cg-admin-setuprepo ~/test/test1
$ cg-push
cg-push: where to push to?
You need to first add the remote branch to your local repository by the
cg-branch-add origin ~/test/test1
command. I've added it to the instructions.
Thanks,
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
From: Paul Dickson <hidden> Date: 2016-06-15 22:42:14
On Mon, 12 Dec 2005 02:12:10 +0100, Petr Baudis wrote:
this is Cogito version 0.16.1, the next stable release of the
human-friendly version control UI for the Linus' GIT tool.
Can the -help argument be supported too? It's pretty annoying to end up
typing -help and having that used as a tag or commit.
Any chance of man files? I'm more use to type man than cg-help.
How about giving instructions in the edited commit message about how to
abort the commit. I've figured out you can just delete all the
referenced files, but this was just by accident. (0.15.1) I had my emacs
segfault and that commit was performed too.
Any chance a creating a very simple cg-mv? Having to switch is a lower
level (git) to perform this function takes time (verifying the
functionality).
Is there a cogito equivalent of "git-branch foo"? It seems cg-branch-add
does everything but that.
-Paul
Using git/cogito for 9 days.
From: Petr Baudis <hidden> Date: 2016-06-15 22:42:14
Dear diary, on Tue, Dec 13, 2005 at 02:26:36AM CET, I got a letter
where Paul Dickson [off-list ref] said that...
On Mon, 12 Dec 2005 02:12:10 +0100, Petr Baudis wrote:
quoted
this is Cogito version 0.16.1, the next stable release of the
human-friendly version control UI for the Linus' GIT tool.
Can the -help argument be supported too? It's pretty annoying to end up
typing -help and having that used as a tag or commit.
Both -h and --help is supported. -help should always yield "unknown
argument", but supporting it directly would be inconsistent and might
make the users think that they can actually use that for all the long
arguments.
Any chance of man files? I'm more use to type man than cg-help.
You can make the man files by
make doc
and install them by
make install-doc
This isn't done by default so that you won't need asciidoc for the
build. This is exactly the same way in GIT.
How about giving instructions in the edited commit message about how to
abort the commit. I've figured out you can just delete all the
referenced files, but this was just by accident. (0.15.1) I had my emacs
segfault and that commit was performed too.
Thanks for the idea:
+[ "$commitalways" ] && echo "CG: Do not save this file and just quit if
you want to abort the commit." >>$LOGMSG
Any chance a creating a very simple cg-mv? Having to switch is a lower
level (git) to perform this function takes time (verifying the
functionality).
Yes. That's planned for 0.17, and I have the patch in my queue.
Is there a cogito equivalent of "git-branch foo"? It seems cg-branch-add
does everything but that.
cg-switch, but it's not in 0.16. It's in the 0.17pre git tree and will
be in 0.17.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
From: Paul Dickson <hidden> Date: 2016-06-15 22:42:14
On Tue, 13 Dec 2005 17:56:45 +0100, Petr Baudis wrote:
Dear diary, on Tue, Dec 13, 2005 at 02:26:36AM CET, I got a letter
where Paul Dickson [off-list ref] said that...
quoted
Any chance of man files? I'm more use to type man than cg-help.
You can make the man files by
make doc
and install them by
make install-doc
This isn't done by default so that you won't need asciidoc for the
build. This is exactly the same way in GIT.
See my messages about 0.99.9m and xmlto (and asciidoc). They are
currently required for building the RPMs. Perhaps the spec file needs
updating.
Thanks for the peek into your input queue.
-Paul
From: Petr Baudis <hidden> Date: 2016-06-15 22:42:14
Dear diary, on Tue, Dec 13, 2005 at 07:02:57PM CET, I got a letter
where Paul Dickson [off-list ref] said that...
On Tue, 13 Dec 2005 17:56:45 +0100, Petr Baudis wrote:
quoted
Dear diary, on Tue, Dec 13, 2005 at 02:26:36AM CET, I got a letter
where Paul Dickson [off-list ref] said that...
quoted
Any chance of man files? I'm more use to type man than cg-help.
You can make the man files by
make doc
and install them by
make install-doc
This isn't done by default so that you won't need asciidoc for the
build. This is exactly the same way in GIT.
See my messages about 0.99.9m and xmlto (and asciidoc). They are
currently required for building the RPMs. Perhaps the spec file needs
updating.
But the spec file also makes the 'doc' and 'install-doc' targets. When
you act as a packager, asciidoc becomes a reasonable build-time
requirement.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.