You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by ni...@apache.org on 2004/01/13 09:20:41 UTC

cvs commit: xml-forrest .cvsignore

nicolaken    2004/01/13 00:20:41

  Modified:    .        .cvsignore
  Log:
  Yes, this is how I backup the build dirs between changes.
  
  Revision  Changes    Path
  1.4       +9 -0      xml-forrest/.cvsignore
  
  Index: .cvsignore
  ===================================================================
  RCS file: /home/cvs/xml-forrest/.cvsignore,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- .cvsignore	2 Oct 2003 06:03:53 -0000	1.3
  +++ .cvsignore	13 Jan 2004 08:20:41 -0000	1.4
  @@ -1,4 +1,13 @@
   build
  +build1
  +build2
  +build3
  +build4
  +build5
  +build6
  +build7
  +build8
  +build9
   dist
   build.number
   .project
  
  
  

Re: cvs commit: xml-forrest .cvsignore

Posted by Nicola Ken Barozzi <ni...@apache.org>.
Juan Jose Pablos wrote:
...
> Is is too hard to see this?
> cheche@yarel:~/xml/xml-forrest$ cvs -q update
> ? build1
> ? build2
> ? build3
> ? build4

No, the problem is that when I ask to see the different files in the 
xml-forrest tree, I get all the contents of these dirs.

Anyway, we should not be discussing such a trivial thing. If you feel it 
so strongly, I will remove it, but it startles me nevertheless.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


Re: cvs commit: xml-forrest .cvsignore

Posted by Juan Jose Pablos <ch...@che-che.com>.
Nicola Ken Barozzi wrote:
> Juan Jose Pablos wrote:
> 
>> Nicola,
>>
>> Are you sure that a personal backup plan like yours should be share 
>> for the whole community? :-)
>>
>> I feel that those lines should not be there. what do you think?
> 
> 
> I think it's not a big deal :-P
> 

yes, but it is confusing for people, it make them think that we support 
some kind of backup when we do not. This is an individual need that is 
not share by the community


Is is too hard to see this?
cheche@yarel:~/xml/xml-forrest$ cvs -q update
? build1
? build2
? build3
? build4


Re: cvs commit: xml-forrest .cvsignore

Posted by Nicola Ken Barozzi <ni...@apache.org>.
Juan Jose Pablos wrote:

> Nicola,
> 
> Are you sure that a personal backup plan like yours should be share for 
> the whole community? :-)
> 
> I feel that those lines should not be there. what do you think?

I think it's not a big deal :-P

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


Re: cvs commit: xml-forrest .cvsignore

Posted by Juan Jose Pablos <ch...@che-che.com>.
Nicola,

Are you sure that a personal backup plan like yours should be share for 
the whole community? :-)

I feel that those lines should not be there. what do you think?

Thanks!

Cheche

nicolaken@apache.org wrote:
> nicolaken    2004/01/13 00:20:41
> 
>   Modified:    .        .cvsignore
>   Log:
>   Yes, this is how I backup the build dirs between changes.
>   
>   Revision  Changes    Path
>   1.4       +9 -0      xml-forrest/.cvsignore
>   
>   Index: .cvsignore
>   ===================================================================
>   RCS file: /home/cvs/xml-forrest/.cvsignore,v
>   retrieving revision 1.3
>   retrieving revision 1.4
>   diff -u -r1.3 -r1.4
>   --- .cvsignore	2 Oct 2003 06:03:53 -0000	1.3
>   +++ .cvsignore	13 Jan 2004 08:20:41 -0000	1.4
>   @@ -1,4 +1,13 @@
>    build
>   +build1
>   +build2
>   +build3
>   +build4
>   +build5
>   +build6
>   +build7
>   +build8
>   +build9
>    dist
>    build.number
>    .project
>   
>   
>