On Sat, Jun 08, 2013 at 12:28:14AM +0200, Markus Teich wrote:
> Hey guys,
>
> I feel this three popular approaches have drawbacks:
> * When creating the repository in $HOME i have to carefully select
> which files to add.
> * When copying files from the working directory to $HOME i have to
> sync
On Sat, Jun 8, 2013, at 21:04, William Giokas wrote:
> Actually quite a good idea, I must say.
thanks,
I forgot to add, most of my patchqueues are using guards like:
hg qselect `uname -s`
Allows me to have the same repo for Linux (work) and FreeBSD (home).
ie. you need different scripts for
On Sat, Jun 08, 2013 at 03:27:56PM +0200, Łukasz Gruner wrote:
> On Sat, Jun 8, 2013, at 14:24, Markus Teich wrote:
> > Please, enlighten me!
> >
> > --Markus
> >
> >
> > Am 08.06.2013 13:18, schrieb Łukasz Gruner:
> > > you might use a real version control instead of git.
> >
>
> not having a
On Sat, Jun 8, 2013, at 14:24, Markus Teich wrote:
> Please, enlighten me!
>
> --Markus
>
>
> Am 08.06.2013 13:18, schrieb Łukasz Gruner:
> > you might use a real version control instead of git.
>
not having any particular one in mind, just one that behaves properly,
git is not yet ready to be
Please, enlighten me!
--Markus
Am 08.06.2013 13:18, schrieb Łukasz Gruner:
you might use a real version control instead of git.
On Sat, Jun 8, 2013 at 12:22 PM, Markus Teich
wrote:
> I'm not exclusively talking about me. Some random script (software update?)
> or anything could move them.
Are you talking about dotfiles from $HOME/?
If some software update or random scripts starts manipulating my home
directory like that I
On Sat, Jun 8, 2013, at 3:04, Markus Teich wrote:
> git will break them. It calls unlink and create on every update.
you might use a real version control instead of git.
--
Pozdrawiam,
Łukasz Gruner
What i would like to put in my dotfiles repo:
* vim config including own filetype settings and plugins
* .xsession for dwm
* $HOME/.fonts/ for custom dwm and st fonts
* .whatevershellrc
* .dircolors
* .gitconfig
* custom $HOME/bin/scripts which of course i could put in an extra repo
without prob
I'm not exclusively talking about me. Some random script (software
update?) or anything could move them.
Also http://harmful.cat-v.org/software/symlinks
--Markus
Am 08.06.2013 04:09, schrieb Fernando C.V.:
* When symlinking files i get problems when moving/backing up the
configfiles in $HOME
On Sat, 08 Jun 2013 00:28:14 +0200
Markus Teich wrote:
> Hey guys,
>
> I feel this three popular approaches have drawbacks:
> * When creating the repository in $HOME i have to carefully select
> which files to add.
> * When copying files from the working directory to $HOME i have to
> sync the w
> * When symlinking files i get problems when moving/backing up the
> configfiles in $HOME since it will move the symlink and maybe write an
> actual file to $HOME instead.label:l-dwm dot
The files are already under version control, if you need backup you
could use some remote repository to sync w
git will break them. It calls unlink and create on every update.
At the moment I am thinking about the GIT_DIR in $HOME/somthing/deeper
and setting the GIT_WORK_TREE to $HOME after cloning, making backups of
possibly already existing files and moving the cloned files to $HOME.
Handling template
On Fri, Jun 7, 2013 at 10:28 PM, Markus Teich
wrote:
> * When symlinking files i get problems when moving/backing up the
> configfiles in $HOME since it will move the symlink and maybe write an
> actual file to $HOME instead.
Hardlinks?
--
Dmitrij D. Czarkoff
Hey guys,
I feel this three popular approaches have drawbacks:
* When creating the repository in $HOME i have to carefully select which
files to add.
* When copying files from the working directory to $HOME i have to sync
the working directory with $HOME manually (no 'git diff' or 'git status')
14 matches
Mail list logo
