Tag Info

New answers tagged

1

Any sub directory to a directory containing a git repo will be identified as a git repo. I had accidentally created a git repo in / which resulted in all directories being identified as git repos.


0

xargs is the unix utility I was looking for. From the man page: The xargs utility reads space, tab, newline and end-of-file delimited strings from the standard input and executes utility with the strings as arguments. Any arguments specified on the command line are given to utility upon each invocation, followed by some number of the arguments read from ...


2

Just pipe through a while loop: git diff --name-only develop | grep coffee$ | while IFS= read -r file; do ./node_modules/.bin/coffeelint "$file" done


3

It does seem excessive. It may be possible to deal with only one git repository. That all depends on the capabilities of the ikiwiki infrastructure (of which I know nothing about). The Why The reason you'll want the repository to be a bare repository is because a non-bare repository almost always will have a branch checked out. Other git repositories ...


0

I'm guessing it's your permissions with sub-directories within the repository. # Set the same ownerships for every file and directory within the repository sudo chown -R root:project /path/to/project # Remove permissions for others on all files sudo chmod o-rwx $(find /path/to/project -not -type d) If you want group members to write back changes: # Set ...


1

Something like this might be what you want. for i in $(git log --format='%H'); do branch="$(git branch --contains $i|awk 'NR==1{print $1}')" [ "$branch" != "*" ] && echo "commit '$i' is in branch '$branch'" done Prints the commit and it's branch if not the current branch.


0

The main two basic gui clients I rely on are gitg for Ubuntu and gitx for OSX gitg shown below: gitg: https://apps.ubuntu.com/cat/applications/gitg/ gitx: http://frim.frim.nl/GitXStable.app.zip


2

The GIT project maintains a page with all the GUIs available for all platforms both free and commercial. I'd list them all here but it's a pretty extensive list with screenshots and descriptions. GUI Clients GIT also comes, typically with 2 GUIs. You can run them as follows: $ git gui ...


1

The warnings in some of the answers here are heavily exaggerated - like this one: having your home directory in git is almost certainly going to make your life an impossible mess I have been having my $HOME folder as a git repo for a long while and it works without any problems, as long as you know how git works it's going to be fine. See it in action ...


0

In order to get this to work on OS X, I made some minor modifications to l0b0's solution: git-grouped-log () { while read -r -u 9 since name do until=$(date -j -v+1d -f '%Y-%m-%d' $since +%Y-%m-%d) echo "$since $name" echo GIT_PAGER=cat git log \ --no-merges \ --committer="$name" ...


0

It is very unusual to use low level commands like dpkg-deb to build debian packages - this looks like a XY-problem. Usually, you build Debian packages from their source by using high level commands like debuild which then calls dpkg-buildpackage and other tools like dpkg-source. The actual .deb files are created by calling special targets of ./debian/rules ...


0

dpkg-deb will build your Debian packages according to the package scripts, so in order to exclude one or more directories you may use dh_install -X .git (adding any other directory on the same line) in your debian/rules script. For a similar information check http://stackoverflow.com/questions/9451347/remove-svn-while-building-debian-packages


3

xargs -0 means to use only null bytes to separate input records, and include newline characters and other whitespace in the input. You're going to have a newline at the end of the revision output there, which head and cut will leave there, and which will be included in the argument given to git. Git doesn't like that. I think you've edited the newline out of ...


2

Make sure to avoid unnecessary multiple overwrite passes with shred. E.g. use shred -n 1 without anything else. The problem with secure file deletion (with git and in general) is that every time you edit, clone, switch branches, etc. a new file (or set of files) is created, possibly in a different physical location. Thus an unknown amount of copies is ...


4

Forget about shred, it spends a lot of time doing useless things and misses the essential. shred wipes files by making multiple passes of overwriting files with random data (a “Gutmann wipe”), because with the disk technologies of 20–30 years ago and some expensive laboratory equipment, it was possible (at least in theory) to recover overwritten data. This ...


2

I think that since there are so many small files in a Git repository, it's going to take a long time for shred to delete them and write over the old data. I would suggest doing something a little different and use tmpfs to store the data in RAM. Then, when you are done, you simply unmount it and you don't have to worry about the data being stored anywhere on ...


5

Git includes a git-shell command suitable for use as a Git-only login shell. It accepts exactly the following commands: git receive-pack git upload-pack git upload-archive git-receive-pack git-upload-pack git-upload-archive cvs server (used for emulating a CVS server, and not required for the Git protocol) So these are the only commands you ...



Top 50 recent answers are included