On 15-02-09, Tom Roche wrote:
For the gory details, see
https://github.com/RichiH/vcsh/issues/147
but my request boils down to this:
I'm using `vcsh` to VC files in $HOME (et al), but
1. I want to leverage the goodness of `vcsh`/`mr` and have repos for bash,
emacs, ssh, etc
2. I also want
On Tue, Feb 10, 2015 at 2:12 PM, Mark Stillwell wrote:
> Note that the version of vcsh that is packaged with some versions of ubuntu
> has a bug in it, so that it will look for hooks in
> $XDH_CONFIG_HOME/vcsh/hooks-enabled rather than
> $XDG_CONFIG_HOME/vcsh/hooks-enabled. The easiest fix is just
On 15-02-10, Richard Hartmann wrote:
On Tue, Feb 10, 2015 at 2:12 PM, Mark Stillwell wrote:
Note that the version of vcsh that is packaged with some versions of ubuntu
has a bug in it, so that it will look for hooks in
$XDH_CONFIG_HOME/vcsh/hooks-enabled rather than
$XDG_CONFIG_HOME/vcsh/hooks-
On 15-02-10, Richard Hartmann wrote:
On Tue, Feb 10, 2015 at 2:12 PM, Mark Stillwell wrote:
Note that the version of vcsh that is packaged with some versions of ubuntu
has a bug in it, so that it will look for hooks in
$XDH_CONFIG_HOME/vcsh/hooks-enabled rather than
$XDG_CONFIG_HOME/vcsh/hooks-
On Tue, Feb 10, 2015 at 3:19 PM, Mark Stillwell wrote:
> https://bugs.launchpad.net/ubuntu/+source/vcsh/+bug/1352280
Just poked around. In Ubuntu-speak, I will need to prepare a SRU to
get this fixed. Sounds easy enough to do in the next day or two.
Richard
On 15-02-10, Richard Hartmann wrote:
On Tue, Feb 10, 2015 at 3:19 PM, Mark Stillwell wrote:
https://bugs.launchpad.net/ubuntu/+source/vcsh/+bug/1352280
Just poked around. In Ubuntu-speak, I will need to prepare a SRU to
get this fixed. Sounds easy enough to do in the next day or two.
Cool.
While I appreciate everyone's assistance ... you seem to be answering someone
else's question :-(
I know from reading what little I have about this matter (generally, VCing
$HOME content) that a lotta people, for a long time, has been concerned with
what I would call "the output side" (or, tem
Hi,
On February 10, 2015 7:00:07 PM GMT+01:00, Tom Roche
wrote:
>
>but I guess I should've spelled it out:
>
>1. I create repo=vcsh-bash to VC files including ~/.bash* . I add a
>~/README.rst to make it available to its remote/web repo, then commit
>and push.
>
>2. I create repo=vcsh-emacs to VC
Tom Roche wrote:
> Unfortunately, that's not my question/problem[2]: I'm asking about the
> *input* side, or *pre-commit*: how can I get a README into the root of a
> vcsh-based repo (to make it available for a remote/web repo) *without*
> putting it into ${HOME} pre-commit?
Tom, if I understand y
Hi Tom,
I don't know that this would address your problem, but have you considered
just using normal git to create your repo in a subdirectory? So you might
have a project/vcsh-bash directory which is a git repo containing .bashrc
and your readme.
On 10 Feb 2015 18:03, "Tom Roche" wrote:
>
> Whi
Vincent Demeester Tue Feb 10 19:30:08 CET 2015 (rearranged) [1]
> The downsides of this approach is that you have to create/edit the README
> "outside" ~/ and vcsh (in another working copy).
That does *not* sound like a problem to me. In fact, (IIUC) I originally
proposed doing something like t
Mark Stillwell Tue, 10 Feb 2015 18:41:41 + [1]
> have you considered just using normal git to create your repo in a
> subdirectory?
Yes, originally I did this with subdirs and symlinks ... which got whacked by
changes to `git` as mentioned, e.g., here[2].
thanks anyway, Tom Roche
[1]: ht
I am still not 100% sure if I understand what you want.
Another option thrown into the ring, without being sure if that would
work for you:
You could have one branch with and one without README.rst and have one
rebase on the other automagically.
As an aside: If you have more than one instance of
TomRoche 9 Feb 2015 ~1730 EST [1]
>>> I thought I could do something like
>>> $ mkdir -p ~/info/software/vcsh/fake_repositories/vcsh-bash-fake/
>>> # edit ~/info/software/vcsh/fake_repositories/vcsh-bash-fake/README.rst
>>> $ pushd ~/info/software/vcsh/fake_repositories/vcsh-bash-fake/
>>>
Re,
Tom Roche writes:
Vincent Demeester Tue Feb 10 19:30:08 CET 2015 (rearranged) [1]
The downsides of this approach is that you have to create/edit the
README "outside" ~/ and vcsh (in another working copy).
That does *not* sound like a problem to me. In fact, (IIUC) I
originally proposed
15 matches
Mail list logo
