On May 26, 2011, at 19:08 , Stephan Beal wrote:
On Thu, May 26, 2011 at 7:03 PM, Richard Hipp d...@sqlite.org wrote:
Exactly. I think it best that this not be a persistent setting, but just a
command-line option or query parameter.
Or possibly a propagating tag? That would(?) solve
On Mon, May 30, 2011 at 3:43 AM, Remigiusz Modrzejewski
l...@maxnet.org.pl wrote:
But I still believe, that the true problem is storing in the repository
things that are not part of the project...
He did not say they were not part of the project.
But anyway, maybe this optional part of the
I'm thinking specifically about things like JavaScript that makes the web ui
slightly nicer (diff coloring / source coloring). So they are not part of
the project (and shouldn't be exported for, say, a C# based project), but
need to be part of the repository so that all of the formatting carries
On 5/30/2011 10:46 AM, Tomek Kott wrote:
I'm thinking specifically about things like JavaScript that makes the
web ui slightly nicer (diff coloring / source coloring). Unless I'm
missing an easier way to deal with that?
If it works for your project, you could keep your fossil UI tweaks
True, and I do have a website, but to me that kind of ruins the whole
self-contained nature of Fossil which I love...
On Mon, May 30, 2011 at 11:05 AM, Joshua Paine jos...@letterblock.comwrote:
On 5/30/2011 10:46 AM, Tomek Kott wrote:
I'm thinking specifically about things like JavaScript
On 5/30/2011 11:25 AM, Tomek Kott wrote:
True, and I do have a website, but to me that kind of ruins the whole
self-contained nature of Fossil which I love...
Once you have a dozen or more fossil repos, though, it just gets silly
to duplicate SCM ui code in each of them.
--
Joshua Paine
The ZIP and tarball generators built into Fossil are not intended to be a
delivery mechanism for product releases. They are simply a convenient way
of downloading a particular version of your project without having to clone
the whole repo. And for that purpose, the ZIP and tarballs should
Hi folks,
Is there a way with fossil zip to export all folders except a specific
one? For example, I have a 'www' folder, which contains some js / css files
for the web portion. However, when exporting a completed release, I'd like
to export without that folder. This would be something similar to
On Thu, May 26, 2011 at 9:23 AM, Tomek Kott tkott.s...@gmail.com wrote:
Hi folks,
Is there a way with fossil zip to export all folders except a specific
one? For example, I have a 'www' folder, which contains some js / css files
for the web portion. However, when exporting a completed
On Thu, May 26, 2011 at 4:46 PM, Tomek Kott tkott.s...@gmail.com wrote:
Now, I believe that the easiest (not necessarily the best place to check
to ignore would be in the zip_add_file(), since all commands flow through
that (both folder / file names). The only question remaining, since I can't
On Thu, May 26, 2011 at 12:53 PM, Stephan Beal sgb...@googlemail.comwrote:
On Thu, May 26, 2011 at 4:46 PM, Tomek Kott tkott.s...@gmail.com wrote:
Now, I believe that the easiest (not necessarily the best place to
check to ignore would be in the zip_add_file(), since all commands flow
On Thu, May 26, 2011 at 7:03 PM, Richard Hipp d...@sqlite.org wrote:
Exactly. I think it best that this not be a persistent setting, but just a
command-line option or query parameter.
Or possibly a propagating tag? That would(?) solve the branching/timeframe
issue, i think, by simply taking
12 matches
Mail list logo
