On 6/13/2017 3:05 PM, Joerg Sonnenberger wrote:
On Tue, Jun 13, 2017 at 02:44:31PM -0500, The Tick wrote:
Thanks, that is what I was looking for. I've set up a test respository and
things look good until I get to the final "merge" step:
$ f init F.fossil
$ f open F.fossil
$ f add project
$ f
On Tue, Jun 13, 2017 at 02:44:31PM -0500, The Tick wrote:
> Thanks, that is what I was looking for. I've set up a test respository and
> things look good until I get to the final "merge" step:
>
> $ f init F.fossil
> $ f open F.fossil
> $ f add project
> $ f commit --tag 1.5 --branch Official
> $
On 6/13/2017 12:52 PM, Joerg Sonnenberger wrote:
On Tue, Jun 13, 2017 at 12:17:46PM -0500, The Tick wrote:
Given a repository based on a previously fetched version of some software
package and having been modified with local changes, what is the best way to
update to a more recent version of
On Tue, Jun 13, 2017 at 12:17:46PM -0500, The Tick wrote:
> Given a repository based on a previously fetched version of some software
> package and having been modified with local changes, what is the best way to
> update to a more recent version of the upstream package?
The best approach is
4 matches
Mail list logo
