Re: [fossil-users] Is this a crazy idea?

2015-03-23 Thread Joan Picanyol i Puig
* Ramon Ribó ram...@compassis.com [20150320 11:19]:
 A possible workflow to do partial commits in fossil could be:
 
 - fossil diff --tk --partial-commit
 
 (A special version of fossil diff --tk appears where there is a
 checkbox in every difference)
 
 - Select some differences
 

This is pretty much what hg GUIs (tortoisehg) do, and it is something
rather useful.

qvb
--
pica
___
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] SVN-fs-dump-format-version: 3 will produce unusable blobs

2015-03-23 Thread Baruch Burstein
On Mon, Mar 23, 2015 at 11:26 PM, Jan Nijtmans jan.nijtm...@gmail.com
wrote:

 2015-03-20 16:55 GMT+01:00 Kain Abel isoru...@gmail.com:
  I hope someone can reproduce this behavior:

 Yes, I can reproduce that.

 See:
 
 https://svn.apache.org/repos/asf/subversion/branches/1.5.x/notes/dump-load-format.txt
 

 The conclusion is that fossil import --svn only understands version 1
 and 2
 from the svn dump-load-format, version 3 is not yet implemented.


Version 3 should be understood, too. I definitely remember testing version
3 dumps thoroughly with my fist revision of the svn import. I don't
remember how thoroughly I tested it after the major refactoring that is the
current state, but I definitely did test it at least a little, and also it
should have stayed stable through the refactoring. I will try to look at
this this week if I get a chance.



-- 
˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
___
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] SVN-fs-dump-format-version: 3 will produce unusable blobs

2015-03-23 Thread Jan Nijtmans
2015-03-20 16:55 GMT+01:00 Kain Abel isoru...@gmail.com:
 I hope someone can reproduce this behavior:

Yes, I can reproduce that.

See:
https://svn.apache.org/repos/asf/subversion/branches/1.5.x/notes/dump-load-format.txt

The conclusion is that fossil import --svn only understands version 1 and 2
from the svn dump-load-format, version 3 is not yet implemented.

Regards,
  Jan Nijtmans
___
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] SVN-fs-dump-format-version: 3 will produce unusable blobs

2015-03-23 Thread Kain Abel
Thanks for the investment of their time.

2015-03-23 23:06 GMT+01:00 Baruch Burstein bmburst...@gmail.com:

 Version 3 should be understood, too. I definitely remember testing version 3
 dumps thoroughly with my fist revision of the svn import. I don't remember
 how thoroughly I tested it after the major refactoring that is the current
 state, but I definitely did test it at least a little, and also it should
 have stayed stable through the refactoring. I will try to look at this this
 week if I get a chance.
___
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] SVN-fs-dump-format-version: 3 will produce unusable blobs

2015-03-23 Thread Kain Abel
Hello,

thank you for your feedback.

Here a short snippet from import.c:

1204:   /* version */
1205:   if( svn_read_rec(pIn, rec)
1206: (zTemp = svn_find_header(rec, SVN-fs-dump-format-version)) ){
1207: ver = atoi(zTemp);
1208: if( ver!=2  ver!=3 ){
1209:   fossil_fatal(Unknown svn-dump format version: %d, ver);
1210: }
1211:   }else{
1212: fossil_fatal(Input is not an svn-dump!);
1213:   }


Version 3 dump file will passed without warning as input, if I have
understood correctly?

With best regards,
Kain

2015-03-23 22:26 GMT+01:00 Jan Nijtmans jan.nijtm...@gmail.com:
 2015-03-20 16:55 GMT+01:00 Kain Abel isoru...@gmail.com:
 I hope someone can reproduce this behavior:

 Yes, I can reproduce that.

 See:
 https://svn.apache.org/repos/asf/subversion/branches/1.5.x/notes/dump-load-format.txt

 The conclusion is that fossil import --svn only understands version 1 and 2
 from the svn dump-load-format, version 3 is not yet implemented.

 Regards,
   Jan Nijtmans
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
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] {fossil-users] symbolic name tags

2015-03-23 Thread Andy Goth
On 3/23/2015 5:44 PM, Tontyna wrote:
 Adding tag names with and without sym-prefix to a repo I couldn't see
 any functional difference. Did I miss something?

Pretty sure if you try (and don't use -raw to inhibit the sym- prefix
being added), you'll get a tag with a name like sym-sym-whatever.

-- 
Andy Goth | andrew.m.goth/at/gmail/dot/com



signature.asc
Description: OpenPGP digital signature
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] {fossil-users] symbolic name tags

2015-03-23 Thread Tontyna
Reading /www/branching.wiki I stumbled upon the paragraph explainig 
symbolic name tags starting with *sym-* being special.


Adding tag names with and without sym-prefix to a repo I couldn't see 
any functional difference. Did I miss something?


Regards
-Tontyna

___
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] {fossil-users] symbolic name tags

2015-03-23 Thread Andy Bradford
Thus said Tontyna on Mon, 23 Mar 2015 23:44:18 +0100:

 Reading /www/branching.wiki  I stumbled  upon the  paragraph explainig
 symbolic name tags starting with *sym-* being special.

Maybe  some  clarification  is  in  order  here.  This  is  specifically
referring to the manifest  (I think). If you are using the  UI and add a
tag that has ``sym-'' in its name, it won't have any special meaning.

For an example, see this manifest:

https://www.fossil-scm.org/index.html/artifact/9d39c6dca7be2796

Scroll to  the bottom and  you will see some  T-cards that have  sym- in
them.

 Adding tag names with and without  sym-prefix to a repo I couldn't see
 any functional difference. Did I miss something?

To add such a  special tag you would have to use a  tool that allows you
to add raw tags, like ``fossil tag''

Andy
--
TAI64 timestamp: 40005510a3ea
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users