Re: [fossil-users] branch assistance needed

2018-07-05 Thread Nicola

On 04/07/2018 16:42, jungle Boogie wrote:
On 12:42AM, Wed, Jul 4, 2018 Nicola 
 > Maybe, the sentence above could be complemented with an example of how

 > to do that and how *not* to do it (e.g., explaining what the effect of
 > adding a 'trunk' tag to a random check-in is and why it should not be
 > done).

So provide a patch with the enhancement and let's see what happens.


IIUC, the sentence refers to an implementation detail: moving check-ins
between branches is implemented by simply renaming tags. But, it is easy
(at least, for a newcomer like myself) on a first (and possibly second)
reading to interpret it in the sense that *the user* can move check-ins
between branches that way.

As for contributing to the project, currently I'd likely do more harm
than good :) I have been using Fossil for a short time, and many details
are not entirely clear to me yet (e.g., I still don't understand well
the purpose of tagging branches with both branch=name and sym-name), but
I am taking notes as I am learning, and I am willing to share them some
time in the future for the benefit of other beginners.

Nicola
___
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] branch assistance needed

2018-07-04 Thread Nicola
On 04/07/2018 00:18, Warren Young wrote:> On Jul 3, 2018, at 3:09 PM, 
Dewey Hylton  wrote:


>> I then attempted to change that latest commit by adding a 'trunk' 
tag and cancelling the new branch tag.

>
> Ow!
As a newbie Fossil user, after reading

https://www.fossil-scm.org/index.html/doc/trunk/www/branching.wiki

and, specifically, this sentence:

> […] check-ins can be freely moved between branches simply by altering
> their tags
I was (mis)lead to believe that what the OP did might somehow work
(well, actually I was skeptic, so I tried on a test repository).

Maybe, the sentence above could be complemented with an example of how
to do that and how *not* to do it (e.g., explaining what the effect of
adding a 'trunk' tag to a random check-in is and why it should not be
done).

Nicola
___
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] Perception of Fossil

2018-06-15 Thread Nicola Vitacolonna
> Git does have its own method (`git am`).

Sorry, that should be `git request-pull`.

Nicola

___
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] Perception of Fossil

2018-06-15 Thread Nicola Vitacolonna
On 15/06/2018 01:32, Chad Perrin wrote: 
> On Thu, Jun 14, 2018 at 09:59:12PM +0100, Thomas wrote: 
>> 
>> Pull requests are not supported, hence the software can't be used for 
>> community driven open source. 
> 
> The pull request interface on GitHub is a feature of GitHub, not of Git. 
> While it would be nice to have a similar feature built into the Fossil 
> web UI, doing it the same way would require having a centralized website 
> on which to implement it.  Something similar could theoretically be 
> supported in Fossil itself, but would not be identical to the way 
> GitHub's pull request feature works. 

FWIW, GitHub pull requests have been harshly criticised by Linus 
Torvalds himself [1]. Git does have its own method (`git am`). Maybe, 
Fossil could implement something along the lines of `git am`. 

[1] https://github.com/torvalds/linux/pull/17#issuecomment-5654674 

Nicola 

PS: recent Fossil fan, list subscriber and first-time poster here. 
Thanks for not treating me as a bot!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users