Re: [fossil-users] Closing fossil output

2014-08-14 Thread Alysson Gonçalves de Azevedo
Oh i see, thank you very much.



Alysson Gonçalves de Azevedo

Anarcho-syndicalism is a way of preserving freedom. - Monty Python


2014-08-11 18:08 GMT-03:00 Scott Robison sc...@casaderobison.com:

 On Mon, Aug 11, 2014 at 2:36 PM, Alysson Gonçalves de Azevedo 
 agalys...@gmail.com wrote:

 I understand why one cannot open a database (or any other command) from
 descriptor file minor than 3.
 But why this `fossil branch 21` do work and `fossil branch 2-`
 doesn't, it's not clear.

 If i open a database using descriptor 3 and close stderr, does descriptor
 3 becomes 2 ?
 I don't want bother anyone, i just asking because this is something new
 to me.


 Your guess is correct. Normally you have STDIN, STDOUT  STDERR as fd 0, 1
  2 respectively. By telling the shell to close / not open STDERR (2-) 2
 becomes the next file descriptor and is used by the environment when SQLite
 opens one of the databases.

 SDR

 ___
 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] Closing fossil output

2014-08-11 Thread Alysson Gonçalves de Azevedo
Well, I don't really get, a closed file descriptor wouldn't cause
corruption, would?
btw, i'll use /dev/null.

thanks



Alysson Gonçalves de Azevedo

Anarcho-syndicalism is a way of preserving freedom. - Monty Python


2014-08-11 16:19 GMT-03:00 Stephan Beal sgb...@googlemail.com:

 On Mon, Aug 11, 2014 at 9:16 PM, Richard Hipp d...@sqlite.org wrote:

 That is by design, and it is for your protection.
 http://www.sqlite.org/compile.html#minimum_file_descriptor


 @Alysson: the scenario described there actually happened to the main
 fossil repo. Luckily, it corrupted only one or two non-critical tables
 which could be rebuilt.

 --
 - 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


___
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] Closing fossil output

2014-08-11 Thread Alysson Gonçalves de Azevedo
I understand why one cannot open a database (or any other command) from
descriptor file minor than 3.
But why this `fossil branch 21` do work and `fossil branch 2-` doesn't,
it's not clear.

If i open a database using descriptor 3 and close stderr, does descriptor 3
becomes 2 ?
I don't want bother anyone, i just asking because this is something new to
me.

Thanks in advance,
Alysson Gonçalves de Azevedo

Anarcho-syndicalism is a way of preserving freedom. - Monty Python


2014-08-11 16:41 GMT-03:00 Scott Robison sc...@casaderobison.com:

 On Mon, Aug 11, 2014 at 1:33 PM, Alysson Gonçalves de Azevedo 
 agalys...@gmail.com wrote:

 Well, I don't really get, a closed file descriptor wouldn't cause
 corruption, would?
 btw, i'll use /dev/null.


 It wouldn't cause corruption in and of itself, but once you close a file
 descriptor, it becomes available for use in a future open operation. If you
 close stderr (descriptor 2) and then a database file is opened as
 descriptor 2, anyone who assumes descriptor 2 is always stderr is going to
 write textual data to a non-terminal / non-text file. The fact that
 descriptor 2 was closed isn't the problem, it is the assumption that
 descriptor 2 will always be stderr that is the problem.

 SDR


 ___
 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 CLI tricks: negative pattern matching

2014-06-19 Thread Alysson Gonçalves de Azevedo
Maybe you have to enable this extension (it's said on the link)

$ shopt -s extglob
$ shopt extglob


extglob on





Alysson Gonçalves de Azevedo

Anarcho-syndicalism is a way of preserving freedom. - Monty Python


2014-06-19 15:04 GMT-03:00 Abilio Marques amarq...@smartappsla.com:

 4.3.18 here, not working. FreeBSD 10.0


 2014-06-19 13:06 GMT-04:30 Stephan Beal sgb...@googlemail.com:

 On Thu, Jun 19, 2014 at 7:14 PM, Ron Wilson ronw.m...@gmail.com wrote:

 Which shell? bash  gives me the error:  !: event not found


 That's my historical experience with '!' as well, but it works here:

 [odroid@host:~/fossil/cwal/s2]$ echo $SHELL
 /bin/bash
 [odroid@host:~/fossil/cwal/s2]$ /bin/bash --version
 GNU bash, version 4.2.45(1)-release (arm-unknown-linux-gnueabihf)
 Copyright (C) 2011 Free Software Foundation, Inc.
 License GPLv3+: GNU GPL version 3 or later 
 http://gnu.org/licenses/gpl.html

 This is free software; you are free to change and redistribute it.
 There is NO WARRANTY, to the extent permitted by law.


 --
 - 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



 ___
 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 CLI tricks: negative pattern matching

2014-06-19 Thread Alysson Gonçalves de Azevedo
And yeah, I agree with Beal for beeing cautious using this feature.
we need to know how extglob works so we won't get in trouble.

[odroid@host:~/fossil/cwal/s2]$ ls unit/!(*.s2)

This won't match files outside unit, so if there are files to be
committed outside that door, you need to handle them too.



Alysson Gonçalves de Azevedo

Anarcho-syndicalism is a way of preserving freedom. - Monty Python


2014-06-19 15:25 GMT-03:00 Andy Goth andrew.m.g...@gmail.com:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 6/19/2014 11:09 AM, Alysson Gonçalves de Azevedo wrote:
  Hi all. Just like Beal shared with us the # trick, today i'll share
  how i can commit all except one file using negative patterns
  
 http://www.cyberciti.biz/faq/linux-bash-delete-all-files-in-directory-except-few/
 ,
 
 
 something like !(file).

 Here's more on this feature: http://en.chys.info/2009/02/extglob/

 You've demonstrated the utility of !(file), but I was unsure of the
 other extglob modes such as @().  The link explains.

 And yes, you need to do shopt -s extglob to turn this feature on.

 - --
 Andy Goth | andrew.m.goth/at/gmail/dot/com
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.22 (MingW32)
 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

 iQEcBAEBAgAGBQJToysSAAoJELtYwrrr47Y4nbIH/AlXbFBhk12AMcbgqvidd4K8
 tU6sMbU+0XhQfdhjwnmjpZKWvHSSvT8qCVCd+fDAvrWm3g3tL7PFMSbXQpCEypZD
 PVKWlG3G7T/wA1zWsJ/kuRWR4+3BbP5mjDwVqtrSnARAzDLMZX+U0wO/XlkMMgUa
 kpYpGIfbufq2UikDNVqDDjDaJyL4Kn2qyHTWsrD5zljwQkjxXRSqjDQKGV+jkTgL
 UVkT++wTp+NCgW194eDrEDy55437cUQqPEbQ0K9G6rCRDN9rM+IQCJZFkc5uvxvM
 Qr1txwJHgI94kb1kDR0F32tOAWZkFr7etiAqLoz6Y6laWFtUp9Nk8Zi5faFKNIs=
 =kcQZ
 -END PGP 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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Index (was Re: git-fossil-git does not obtain the same commit hashes.)

2014-06-05 Thread Alysson Gonçalves de Azevedo
I'm not Nico, but allow me answer that as well.

When I was learning to use git, my teacher told me:
When you have a set of changes where a peace of code requires another
peace, you must commit all that together. But if you have a change that
doesn't have any dependeces, you should commit that change alone.

And, well, the same reason you can use to not allow partial chink-in of a
file can be used to not allow commits on a set of files. So, if we have
commit what we tested, we alwayes must to commit all the changes in all the
files.




Alysson Gonçalves de Azevedo

Anarcho-syndicalism is a way of preserving freedom. - Monty Python


2014-06-05 21:58 GMT-03:00 Richard Hipp d...@sqlite.org:




 On Thu, Jun 5, 2014 at 8:33 PM, Nico Williams n...@cryptonector.com
 wrote:

 On Thu, Jun 5, 2014 at 7:22 PM, Matt Welland estifo...@gmail.com wrote:
  foo.txt has changes A, B, C and D.
 
  After each change the developer had the foresight to do a fossil stash
  snapshot. Now the developer decides to put changes B and D into branch
 b-d
  and keep changes A and C on the trunk:

 Ah, foresight.  I should be blessed, but I am not, for that that's not
 how I work.


 I have different reasons for opposing the ability to checking individual
 lines of a file, and I'd like to get Nico's feedback:

 The reason you should never do a partial check-in of a file is because you
 clearly have not tested that partial change.  And you should always test
 your code before you commit.  Especially when committing to trunk.


 --
 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


___
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] Index (was Re: git-fossil-git does not obtain the same commit hashes.)

2014-06-04 Thread Alysson Gonçalves de Azevedo
I started to use fossil just today, but let me participate too :)

Everyday I have a list of tasks that I have to work on and when I finish, I
like to separate the changes of each task by commit.

To do that, I just open GUI, check the lines of the files that i want to
commit.
(Just like this print:
http://i1-linux.softpedia-static.com/screenshots/gitg_5.jpg, where I click
on the - and + to stage the line).

But today, using fossil, I couldn't find anyway to do that, so I had to put
all the changes on the same commit.

Well, in the theory I can work on one task at time and commit when I
finish, but in the practice I work on all the tasks at same time.



Alysson Gonçalves de Azevedo

Anarcho-syndicalism is a way of preserving freedom. - Monty Python


2014-06-04 21:14 GMT-03:00 Warren Young war...@etr-usa.com:

 On 6/4/2014 10:50, Richard Hipp wrote:


 The staging area complicates the interface.


 Perhaps you will add some of this to the Fossil vs Git wiki page. (Section
 3.4?)

 ___
 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