On Tue, 4 Aug 2015, Ron W wrote:
On Tue, Aug 4, 2015 at 11:37 AM, Stephan Beal sgb...@googlemail.com wrote:
On Tue, Aug 4, 2015 at 5:23 PM, Ron W ronw.m...@gmail.com
wrote:
I think this would be a useful feature.
To me this all sounds like fossil enforcing
On Aug 3, 2015, at 4:20 PM, Andy Goth andrew.m.g...@gmail.com wrote:
On 8/3/2015 3:24 PM, Warren Young wrote:
I thought I saw reference on this list to a way to lop off the
most-recent checkin
Using the web interface, you can edit the existing check-in to be in a
branch (I usually use the
On Tue, Aug 4, 2015 at 11:37 AM, Stephan Beal sgb...@googlemail.com wrote:
On Tue, Aug 4, 2015 at 5:23 PM, Ron W ronw.m...@gmail.com wrote:
I think this would be a useful feature.
To me this all sounds like fossil enforcing project-specific policy, which
is something it most certainly
On Tue, Aug 4, 2015 at 11:37 AM, Stephan Beal sgb...@googlemail.com wrote:
On Tue, Aug 4, 2015 at 5:23 PM, Ron W ronw.m...@gmail.com wrote:
I think this would be a useful feature.
To me this all sounds like fossil enforcing project-specific policy, which
is something it most certainly
On 8/3/2015 3:24 PM, Warren Young wrote:
After making this mistake, I know I'm supposed to move the bad commit to
a hidden branch
Who supposes this, and why do you take their opinion as normative?
When a commit to Fossil causes a problem, I've seen drh move it to a
branch (usually not hidden
On 8/3/2015 3:24 PM, Warren Young wrote:
On Aug 3, 2015, at 1:31 PM, Andy Goth andrew.m.g...@gmail.com wrote:
Usually I don't bother, especially if there have been check-ins since
the error was committed.
Wouldn’t a better solution to that problem be a continuous integration
system, so you
On 3 August 2015 at 21:31, Andy Goth andrew.m.g...@gmail.com wrote:
Many times I've created files, modified existing files to reference
them, tested, and committed, only to later discover I forgot to add the
newly created files to the repository.
After making this mistake, I know I'm supposed
Many times I've created files, modified existing files to reference
them, tested, and committed, only to later discover I forgot to add the
newly created files to the repository.
After making this mistake, I know I'm supposed to move the bad commit to
a hidden branch and try again. Usually I
On Aug 3, 2015, at 1:31 PM, Andy Goth andrew.m.g...@gmail.com wrote:
Many times I've created files, modified existing files to reference
them, tested, and committed, only to later discover I forgot to add the
newly created files to the repository.
Yup, been there. :)
After making this
9 matches
Mail list logo
