[git-users] Re: How to make pack remote repository on every push?
> Gergely Polonkai : > You may want to play with gc.pruneexpire. From man git-config: >gc.pruneexpire >When git gc is run, it will call prune --expire 2.weeks.ago. >Override the grace period with this config variable. The value >"now" may be used to disable this grace period and always prune >unreachable objects immediately. This seemed to work the first time on one of my repositories (the longest lived one), so I thought this did the trick, but hasn't worked on later pushes, unfortunately...:-/ To summarize: I have two different git repositores containing org-mode files. One of these repositories use git+ssh and has a history going back 6 years with 708 commits, and one using https and with a history going back 8 months and 37 commits. I have set the values gc.auto=1 gc.pruneexpire=now on both of the remote repositories and all of their clients (where should the values be set? On the remote or on the clients?). The gc.auto setting has been there for a while with no seeming effect, and adding the gc.pruneexpire setting seemed to work on a single push. (I have the possibility to add a hook on the remote, to compress on every push, or alternatively compress using a cron job, but I thought it would be more correct if I could convince git to do this on its own) -- 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 it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Strict, domain-based read/write vs. read-only access.
Hi, Magnus, Does it help to identify this as a policy requirement, not a technical one? Our security and executive groups require that the only way we add or modify code is within the DEV environment/subdomain/call it whatever you want. You MUST NOT add code to a repository from any other environment/subdomain. What if you're in the TEST environment and you find a bug? Fix it in DEV, promote the change, and test again. What if you're in the PROD environment and your shiny new web application crashes because it couldn't handle the load? You MUST NOT modify that code on the fly and update the repository from PROD. You MUST take that error back to DEV, update your code there, TEST it, and then promote the fix back into PROD. Does that help? David > On Jan 7, 2016, at 14:37, Magnus Therningwrote: > > So you basically want to include the source IP address in the decision > of whether a push succeeds? > > I'm sorry but this sounds *amazingly* strange to me. Probably because I > don't quite get what you mean. > -- David - Offbeat dafydd - Online http://pgp.mit.edu/ 51525354555657-- The most dangerous phrase is, 'We've always done it this way.' –RADM Grace Hopper -- 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 it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [git-users] Strict, domain-based read/write vs. read-only access.
Hi, Magnus, The Enterprise I'm working at has separated its DEV, TEST, and PRODUCTION environments with firewalls. Code may be PUSHed to a Code Management System in DEV ONLY. In the TEST and PRODUCTION environments, the CMS repository MUST (cf. RFC-2119) be PULL ONLY. In proposing a CMS, I MUST include the possibility that the same user has access to the same project from more than one environment, so controlling access by user won't work. If the same user has the same access to the same repository in DEV and TEST, what stops that user from adding code via the TEST environment? Thanks! David > On Jan 7, 2016, at 02:59, Magnus Therningwrote: > > What do you mean by "enviroment" here? > > It's common to authorize by user, or by group, but I simply don't > understand what you mean by "environment". > -- David - Offbeat dafydd - Online http://pgp.mit.edu/ 51525354555657-- Werner Heisenberg is driving down the autobahn. A police officer pulls him over. The officer says, "Excuse me, sir, do you know how fast you were going?" "No," replies Dr. Heisenberg, "but I know where I am." -- 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 it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [git-users] ZIP Command not Found
Thank you Paul. Yes, I have installed WinZip. I tried wzzip command(wzzip test.zip *.txt) but it does not work and only shows: WinZip(R) Command Line Support Add-On Version 3.2 (Build 8668) Copyright (c) 1991-2009 WinZip International LLC - All Rights Reserved I am not sure if something I missed to do. 2016-01-08 0:09 GMT+08:00 Paul Smith: > On Thu, 2016-01-07 at 08:01 -0800, alianxu0...@gmail.com wrote: > > I just installed Git for Windows(Git-2.7.0-32-bit) on Windows 7 > > Enterprise. I try to use zip command to zip a file but it show 'bash: > > zip: command not found'. > > Any thoughts on this why this happens? > > Have you installed zip on your system? > > Git doesn't provide the zip utility itself, so if you want to use it > you'll need to install it separately. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Git for human beings" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/git-users/KWFQ_iKAees/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Multiple backup strategy & S3
On 8 January 2016 at 04:36, Charles Manningwrote: > Why not just use rsync? Thanks what {aws s3,s3cmd} sync does but it has a problem of trumping data. -- 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 it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Re: How to make pack remote repository on every push?
Another solution could be running git-repack. This SO answer[1] has some nice details on it. Best, Gergely [1] http://stackoverflow.com/a/8638219 On 8 Jan 2016 02:29, "Steinar Bang"wrote: > > Gergely Polonkai : > > > You may want to play with gc.pruneexpire. From man git-config: > > >gc.pruneexpire > >When git gc is run, it will call prune --expire 2.weeks.ago. > >Override the grace period with this config variable. The value > >"now" may be used to disable this grace period and always > prune > >unreachable objects immediately. > > > This seemed to work the first time on one of my repositories (the > longest lived one), so I thought this did the trick, but hasn't worked > on later pushes, unfortunately...:-/ > > To summarize: > I have two different git repositores containing org-mode files. One of > these repositories use git+ssh and has a history going back 6 years with > 708 commits, and one using https and with a history going back 8 months > and 37 commits. > > I have set the values > gc.auto=1 > gc.pruneexpire=now > on both of the remote repositories and all of their clients (where > should the values be set? On the remote or on the clients?). > > The gc.auto setting has been there for a while with no seeming effect, > and adding the gc.pruneexpire setting seemed to work on a single push. > > (I have the possibility to add a hook on the remote, to compress on every > push, or alternatively compress using a cron job, but I thought it would > be more correct if I could convince git to do this on its own) > > -- > 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 it, send an > email to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] Is it possible to edit unpublished commit?
Hi, I know some tricks like "rebase" and "tree-filter" that can modify the commit history. I want know if I can also go back to history and edit the content. So when I push my changes, the history looks perfect :) Thanks, David -- Regards, David -- 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 it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] Re: Is it possible to edit unpublished commit?
"git rebase -i" with "edit" command is to powerful to handle :) On Fri, Jan 8, 2016 at 2:36 PM Xi Shenwrote: > Hi, > > I know some tricks like "rebase" and "tree-filter" that can modify the > commit history. > > I want know if I can also go back to history and edit the content. So when > I push my changes, the history looks perfect :) > > > Thanks, > David > > -- > > Regards, > David > -- Regards, David -- 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 it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Strict, domain-based read/write vs. read-only access.
you can have multiple ssh credentials and unless users share the same home directory (and hence .ssh directory) you can still have different permissions "per domain" w/ gitolite. On Thu, Jan 7, 2016 at 6:17 AM, David Barrwrote: > Hi, Magnus, > > The Enterprise I'm working at has separated its DEV, TEST, and PRODUCTION > environments with firewalls. > > Code may be PUSHed to a Code Management System in DEV ONLY. In the TEST > and PRODUCTION environments, the CMS repository MUST (cf. RFC-2119) be PULL > ONLY. In proposing a CMS, I MUST include the possibility that the same user > has access to the same project from more than one environment, so > controlling access by user won't work. If the same user has the same access > to the same repository in DEV and TEST, what stops that user from adding > code via the TEST environment? > > Thanks! > David > > > On Jan 7, 2016, at 02:59, Magnus Therning wrote: > > > > What do you mean by "enviroment" here? > > > > It's common to authorize by user, or by group, but I simply don't > > understand what you mean by "environment". > > > > -- > > David - Offbeat > dafydd - Online http://pgp.mit.edu/ > > 51525354555657-- > > Werner Heisenberg is driving down the autobahn. A police officer pulls > him over. The officer says, "Excuse me, sir, do you know how fast you > were going?" > "No," replies Dr. Heisenberg, "but I know where I am." > > -- > 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 it, send an > email to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Multiple backup strategy & S3
On Thu, Jan 7, 2016 at 2:51 PM, Kai Hendrywrote: > Hi guys, > > Like many of you I'm putty more and more precious things like photos into > git for safekeeping. > I've never heard of anyone using git for storing photos.It's like using a wrench as a hammer: it does the job, but that's not what it is designed for. > However the problem I have is how to sync it to a couple of remotes in a > straightforward manner. > Why not just use rsync? > > Also I would like to "fsck" the remotes to make sure the remotes are not > somehow corrupted. > > Ideally I would like to backup straight to S3 but this is a little clumsy > with http://dabase.com/e/14002/ > * I don't want to run commands manually > * I don't want to trump what's there in case my source is corrupted > > So I guess I am looking for more end points to push my git repo to. They > can be public. Any suggestions? Please let me know. > > I'm aware of https://git-annex.branchable.com/ but I don't like how it > mangles my filenames and such. > > Kind regards, > > -- > 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 it, send an > email to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Strict, domain-based read/write vs. read-only access.
David Barr writes: > Hi, Magnus, > > The Enterprise I'm working at has separated its DEV, TEST, and > PRODUCTION environments with firewalls. Ah, so by "environment" you mean network segment, or subdomain. > Code may be PUSHed to a Code Management System in DEV ONLY. In the > TEST and PRODUCTION environments, the CMS repository MUST (cf. > RFC-2119) be PULL ONLY. In proposing a CMS, I MUST include the > possibility that the same user has access to the same project from > more than one environment, so controlling access by user won't work. > If the same user has the same access to the same repository in DEV and > TEST, what stops that user from adding code via the TEST environment? So you basically want to include the source IP address in the decision of whether a push succeeds? I'm sorry but this sounds *amazingly* strange to me. Probably because I don't quite get what you mean. /M -- Magnus Therning OpenPGP: 0x927912051716CE39 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus Computer Science: "In low-level languages like C" Computer Engineering: "In high-level languages like C" -- 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 it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature