On Jul 6, 2017, at 11:36 AM, Natacha Porté wrote:
>
> In shell terms, I'm looking for something equivalent to:
> $ mkdir ../tmp-checkout
> $ cd ../tmp-checkout
> $ fossil open /path/to/fosisl
> $ fossil checkout $targetcommit
> $ cp -r ../working-checkout/* ./
> $ cd ..
> $ rm -rf working-checkou
On Jul 6, 2017, at 1:30 PM, Natacha Porté wrote:
>
> on Thursday 06 July 2017 at 14:01, Richard Hipp wrote:
>>
>> (1) Make edits on Linux but do not commit.
>> (2) Copy the files to Windows and verify that they work there too.
>> (3) Run "fossil commit" on Linux.
>> ...
>> Is that similar to wha
Thus said Natacha Port? on Thu, 06 Jul 2017 19:30:29 -:
> Now imagine you leave things as they are after (3) to do some non-dev
> stuff (or some dev on other repositories), and you receive a serious
> windows-specific bug report. You drop everything to work on it,
> forgetting the "fossil up".
Hello,
on Thursday 06 July 2017 at 14:01, Richard Hipp wrote:
> On 7/6/17, Natacha Porté wrote:
> >
> > On the other hand, the situation in which I was is the checkout being
> > already in the desired state, but fossil having recorded a wrong
> > commit as current, so I would need a change of cur
On 4 July 2017 at 21:19, Andy Bradford wrote:
> Thus said jungle boogie on Tue, 04 Jul 2017 15:03:01 -0700:
>
>> Now I greatly prefer the former, because when copying the hash with
>> the mouse, I can skip the closing (]) bracket, since I usually start
>> right-to-left.
>
> Not to derail your
On 7/6/17, Natacha Porté wrote:
>
> On the other hand, the situation in which I was is the checkout being
> already in the desired state, but fossil having recorded a wrong
> commit as current, so I would need a change of current commit while
> preserving the whole file system, instead of preservi
Hello,
on Thursday 06 July 2017 at 10:59, Richard Hipp wrote:
> On 7/6/17, Natacha Porté wrote:
> > I was recently in a very uncomfortable situation, with precious
> > uncommitted data in the current checkout and the need to change where
> > the checkout "current commit" points to.
>
> That's wh
On Jul 6, 2017, at 8:38 AM, Natacha Porté wrote:
>
> I was recently in a very uncomfortable situation, with precious
> uncommitted data in the current checkout and the need to change where
> the checkout "current commit" points to.
Usually when I find myself in that situation, I just open a new
On 7/6/17, Natacha Porté wrote:
> Hello,
>
> I was recently in a very uncomfortable situation, with precious
> uncommitted data in the current checkout and the need to change where
> the checkout "current commit" points to.
That's what the "fossil update" command is for.
If you are current only
Hello,
I was recently in a very uncomfortable situation, with precious
uncommitted data in the current checkout and the need to change where
the checkout "current commit" points to.
As far as I can tell, that's exactly what `fossil checkout --keep` is
for, but my attempts were met with the messag
In the UNVERSIONED export subcommand:
export FILE OUTPUT Write the content of FILE into OUTPUT on disk
would it be easy to make the OUTPUT filename optional so that if not present
the same name as FILE is assumed?
Thanks.
___
fossil-users mailing li
11 matches
Mail list logo
