[git-users] how to create alias to log @{push}..

how to create alias to log @{push}.. ? i want alias git out/git outgoing like in the mercurial git version 2.7.0.windows.1 git config --global alias.outgoing log @{push}.. error: invalid pattern: @{push}.. -- You received this message because you are subscribed to the Google Groups "Git

Re: [git-users] how to create alias to log @{push}..

Put it in apostrophes: git config --global alias.outgoing 'log @{push}..' Best, Gergely Gergely Polonkai [image: https://]about.me/gergely.polonkai 2016-01-06 9:28 GMT+01:00 NoName

[git-users] How to save file's first commit, but ignore all further changes to this file?

Hi all, I need to save some file in my git repo in it's current state, ignoring all changes to it forever. Any suggestions? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from

[git-users] Strict, domain-based read/write vs. read-only access.

Good Morning, I need to pitch an Enterprise level code management system. This system needs to have some fairly strict read-only vs. read/write requirements based on environment. I first asked this question in Stack Overflow

Re: [git-users] Strict, domain-based read/write vs. read-only access.

Hi, Chris, Thanks for the ideas. Unfortunately, I'm not sure they'll work for me. While these solutions provide authorization by project, I need something that will provide authorization by environment. I need to give an arbitrary user `push` access to a project from DEV, but refuse that same

[git-users] Multiple backup strategy & S3

Hi guys, Like many of you I'm putty more and more precious things like photos into git for safekeeping. However the problem I have is how to sync it to a couple of remotes in a straightforward manner. Also I would like to "fsck" the remotes to make sure the remotes are not somehow corrupted.

Re: [git-users] How to save file's first commit, but ignore all further changes to this file?

There is an assume-unchanged option you can set with git-update-index, but that's for your local repository only; it is possible that other developers will overwrite the file. If you tell us some more details, the list may give you better answers or alternatives, though. Best, Gergely On 6 Jan

Re: [git-users] How to save file's first commit, but ignore all further changes to this file?

I have some "data batches" inside my project. These batches are in a binary proprietary format, and I don't need to save their content into the repo. User can add a files to a batch using an external binary utility. But every batch should have some "batch header" files (binary also, but very small

Re: [git-users] How to save file's first commit, but ignore all further changes to this file?

I think you could check in the "header files" as you want them to be then add the files to your .gitignore that way any changes made to those header files would not be committed to the repo. Another option I think would work which might be the better solution is to use a git hook to copy the

Re: [git-users] Strict, domain-based read/write vs. read-only access.

Have you looking into using a dedicated server package such as gitosis or gitolite? I know github also has a version of there software available as well. Sounds like a solution similar to what is used on drupal.org might work for your needs. Any one can clone a project from drupal.org using

Re: [git-users] How to save file's first commit, but ignore all further changes to this file?

Thank you. I tried to add these files to .gitignore, but "git status" shows them as "modified" or "deleted" anyway. Using git hook is a good idea too. How can I create a hook which will run after clone and after each pull (just in case I added some new batches)? 2016-01-06 22:34 GMT+02:00 Chris

Re: [git-users] How to save file's first commit, but ignore all further changes to this file?

How about (given the comment about it being a template): create an orphan branch add just that file to the branch and commit. Tag the commit delete the branch get folks to 'git checkout tag -- file'. Perhaps even make that an alias. Once it is in the repo it's fixed, unchanged forever! [or