Thus said Andy Goth on Wed, 16 Aug 2017 10:47:56 -0500:
> What of this old thread? Are the issues it discusses still pertinent,
> or have they been resolved?
I believe all the relevant issues were actually resolved, however, I
think it was still unfavorable given the time that was availa
On Thu, Aug 17, 2017 at 12:35 AM, Kyle Shannon wrote:
> Yes, it appears it does. I'll send a change, thanks.
Thank *YOU* so much for your PR, Kyle!
㎝
--
|:**THE BEER-WARE LICENSE** *(Revision 42)*:
| wrote this mail. As long as you retain
| this notice you can do whatever you want with this
Yes, it appears it does. I'll send a change, thanks.
On Wed, Aug 16, 2017 at 4:28 PM, Carlo Miron wrote:
> On Wed, Aug 16, 2017 at 11:48 PM, Carlo Miron wrote:
>
>> On Wed, Aug 16, 2017 at 9:03 PM, Gour wrote:
>>
>>> Hello,
>>>
>>> I just noticed great news:
>>>
>>> https://go-review.googlesou
On Wed, Aug 16, 2017 at 11:48 PM, Carlo Miron wrote:
> On Wed, Aug 16, 2017 at 9:03 PM, Gour wrote:
>
>> Hello,
>>
>> I just noticed great news:
>>
>> https://go-review.googlesource.com/c/56190
Shouldn't line 951 of src/cmd/go/internal/get/vcs.go be
re:
`^(?P(?P([a-z0-9.\-]+\.)+[a-z0-9.\-
On Wed, Aug 16, 2017 at 9:03 PM, Gour wrote:
> Hello,
>
> I just noticed great news:
>
> https://go-review.googlesource.com/c/56190
W00t!!!1
㎝
--
|:**THE BEER-WARE LICENSE** *(Revision 42)*:
| wrote this mail. As long as you retain
| this notice you can do whatever you want with this stuff.
On Wed, Aug 16, 2017 at 9:59 PM, bch wrote:
> That doesn't sound unreasonable. Sort of doubly-constrained 1) from newest
> to older, per branch 2) on conflict, retarget branch, go-to 1
>
That's basically it, at least hypothetically. In principal "easy", and the
code is in place to do all the un/
On Aug 16, 2017 12:54, "Stephan Beal" wrote:
On Wed, Aug 16, 2017 at 9:19 PM, bch wrote:
>
>
> On Aug 16, 2017 12:10, "Stephan Beal" wrote:
>
> It's hypothetically possible, and i investigated it 3 or 4 years ago, but
> the devil is in the details :/. Not impossible, but you have to take care
On Wed, Aug 16, 2017 at 9:54 PM, Stephan Beal wrote:
> just a preference/habit. Thus if you pop the head, you need to make sure
> and go undelta all artifacts in that head which are not referenced by
> anything else in the tree.
>
Parson me: you'd need to undelta anything in the NEW head and rea
On Wed, Aug 16, 2017 at 9:19 PM, bch wrote:
>
>
> On Aug 16, 2017 12:10, "Stephan Beal" wrote:
>
> It's hypothetically possible, and i investigated it 3 or 4 years ago, but
> the devil is in the details :/. Not impossible, but you have to take care
> of details like properly undelta'ing anything
On Aug 16, 2017 12:10, "Stephan Beal" wrote:
It's hypothetically possible, and i investigated it 3 or 4 years ago, but
the devil is in the details :/. Not impossible, but you have to take care
of details like properly undelta'ing anything which is deltad against the
to-be-popped head.
Oh - I d
It's hypothetically possible, and i investigated it 3 or 4 years ago, but
the devil is in the details :/. Not impossible, but you have to take care
of details like properly undelta'ing anything which is deltad against the
to-be-popped head. At the time i wasn't confident enough in my knowhow of
the
Hello,
I just noticed great news:
https://go-review.googlesource.com/c/56190
Sincerely,
Gour
--
The work of a man who is unattached to the modes of material
nature and who is fully situated in transcendental knowledge
merges entirely into transcendence.
_
We really should have (and it's not against philosophy) ability to
pop commits off top, though. I've miscommited to a branch, and I think
I'd just like to redo it, to say nothing of accidentally committing
something sensitive like a credit card number or password.
-bch
On 8/16/17, Stephan Beal
On Wed, Aug 16, 2017 at 8:15 PM, Stephan Beal wrote:
> On Wed, Aug 16, 2017 at 7:59 PM, Steve Schow wrote:
> > Is that possible at all or if not, what is the best way to handle that
> kind of situation with fossil?
>
> Fossil is designed to never forget anything, not even mistakes. It's
> possib
On Wed, Aug 16, 2017 at 7:59 PM, Steve Schow wrote:
> Is that possible at all or if not, what is the best way to handle that
kind of situation with fossil?
Fossil is designed to never forget anything, not even mistakes. It's
possible to move a commit to a new branch, thereby "kind of hiding it",
Steve,
Usually what is done here is the incorrect commit is moved to a
different branch, which is typically hidden. This can be done using
"fossil amend". Then you update to the new head of your branch (the
previous commit) using "fossil update" and retry your commit.
It's also possible t
On 8/16/17, Steve Schow wrote:
> I know the fossil paradigm generally frowns on the idea of undoing commits.
> Please tell me your thoughts about the best approach to handle the following
> situation.
>
> a few file is added to the checkout and committed. So the commit has one
> new file, nothing
I know the fossil paradigm generally frowns on the idea of undoing commits.
Please tell me your thoughts about the best approach to handle the following
situation.
a few file is added to the checkout and committed. So the commit has one new
file, nothing else. It is later determined that the
I have not read all this thread, but it seems to be centered around
release engineering. The goal, as I understand it, is to create a release
and when that release is installed somewhere be aware of what release it
is.
For this kind of thing I use a release engineering script called
"makearc
On Wed, Aug 16, 2017 at 7:19 PM, Stephan Beal wrote:
> On Wed, Aug 16, 2017 at 7:17 PM, David Mason wrote:
>>
>> Wow... longest thread I've ever seen.
>
>
> Naw - there've been a few longer ones.
>
>>
>> Then go to
>> localhost:8081/artifact/1bea11bf4a97b012e7d8b17c71a7d444f0b5a5aa
>> and you'll
On Wed, Aug 16, 2017 at 7:17 PM, David Mason wrote:
> Wow... longest thread I've ever seen.
>
Naw - there've been a few longer ones.
> Then go to localhost:8081/artifact/1bea11bf4a97b012e7d8b17c71a7d4
> 44f0b5a5aa
> and you'll get the exact file you're looking for. Of course, if someone
> edi
Wow... longest thread I've ever seen. I scanned through and didn't see
mention of the simplest solution, if you have shasum available.
> shasum urltags.js
1bea11bf4a97b012e7d8b17c71a7d444f0b5a5aa
> fossil ui
Then go to localhost:8081/artifact/1bea11bf4a97b012e7d8b17c71a7d444f0b5a5aa
and you'll g
> - On Aug 16, 2017, at 11:37 AM, Andy Goth andrew.m.g...@gmail.com wrote:
>
> First off, I'm sorry I've been so incredibly busy with work and business
> travel, no time for Fossil development or even reading the mailing list.
> The only issues I've been able to dink on lately are those that w
On 07/17/17 03:50, Jan Nijtmans wrote:
The patch below modifies Fossil not to create the initial empty
commit. (I always build Fossil with this patch). Everything works
fine without initial empty commit, the reason this was in Fossil is
just historical. Nowadays, there - indeed - is no reason any
On 07/12/17 13:50, Richard Hipp wrote:
The current plan is to release the 10th anniversary edition of Fossil,
version 2.3, on 2017-07-21.
I've been more-or-less keeping SlackBuilds up-to-date on Fossil
releases, even though it's been a long time since I announced that I'm
doing this. Earlier
First off, I'm sorry I've been so incredibly busy with work and business
travel, no time for Fossil development or even reading the mailing list.
The only issues I've been able to dink on lately are those that were
stopping me from getting my work done. I'm trying to change jobs so I
might ha
26 matches
Mail list logo
