Is the default branch used with clients clone the repository. The master branch should be the HEAD branch. Then now that the name is available can do the same again and "create"Ī new branch named master based upon the desired branch. Having a reference in master-broken that we just created this action Option if this would remove the last reference to the objects. Safety feature built into it which will warn and require a force Then now that the hash exists in another branch the easiest thing is This following creates master-broken based upon master. Perhaps master-oldconversion for example. Here I amĬalling it master-broken but use as descriptive of a name asĪppropriate. Save the current branch to master-broken as a backup save. Git log -oneline -graph -decorate -color master new-master Verify the current and future state of the repository: cd /srv/git/exampleproject.git These are the steps that might be used to do it. If in your best judgement it should be modified then Wishes to have the new temporary branch become the master branch as Use judgement.Įxamples are that sometimes a user has munged a commit, has pushed theĭesired branch onto a temporary branch (call it new-master), and But sometimes renaming a branch orĭeleting a branch is the best solution to a problem. Rewinding a branch causes problems for anyone who has pulled from theīranch previously as it breaks being able to pull to it. Renaming or deleting a branch needs some rationale and justificationīecause during normal operation we never want to rewind a branch. while read oldrev newrev refname doĮcho $oldrev $newrev $refname | /usr/local/bin/git-post-receive-hookĮcho $oldrev $newrev $refname | hooks/post-receive-mail-local See auctex.git/hooks/post-receive for an example. Need to be passed in to all hook scripts if multiple ones are desired. Needed since oldrev newrev refname are passed in on stdin. If multiple post-receive hooks are desired then special handling is The config file from this: mailinglist = this: mailinglist = nobody Sometimes maintainers do not like the receiving reference changeĬommits in addition to changeset commits. Mail-Followup-To: hooks/ directory again: chattr +i hooks/ But we do have a variety ofĬonfigurations currently active.) grep Mail-Followup-To. Then configurations switched toīoth the bug list and the original sender. Verify that the hooks/post-receive file then looks like this. sed /srv/git/emacs/elpa.git/hooks/post-receive > hooks/post-receive Set it to where follow-up discussion is desired. This sets the Mail-Followup-To: header address to theĭevel discussion mailing list which is separate from the commit diff Link git_multimail.py to the local hooks directory: ln -s /usr/src/git-multimail/git-multimail/git_multimail.py hooks/Ĭopy another projects template into the hooks directory and then edit Unprotect hooks/ directory: chattr -i hooks/ The result will be this in the git config file. Git config multimailhook.mailinglist config multimailhook.emailprefix "" The mailing list configuration is also configured to add one. Don't set an emailprefix or there will be two when This can be done using the git-config utility Mkdir /srv/git/lwip/lwip-contrib.git/gitcvs-db -m 755Ĭhown nobody /srv/git/lwip/lwip-contrib.git/gitcvs-db Git config gitcvs.dbname "%G/gitcvs-db/sqlite" Now for documentation of the legacy environment. This is no longer desirable for a default. This file is used as a fallback, group administrators can override itĭeprecated cvs server: If upon specific request add 'git-cvsserver' Update the description file: echo "lwIP Contrib - Contributed code for Lightweight TCP/IP stack" > /srv/git/lwip/lwip-contrib.git/description Make it executable: chmod a+x /srv/git/lwip/lwip-contrib.git/hooks/post-updateįorbid access to hooks: chown -R root:root /srv/git/lwip/lwip-contrib.git/hooksĬhattr +i /srv/git/lwip/lwip-contrib.git/hooks Write following to: /srv/git/lwip/lwip-contrib.git/hooks/post-update: #!/bin/sh On vcs0, make a directory to place additional repositories: mkdir /srv/git/lwipĬreate a new shared bare repository (supposedly named lwip-contrib hereafter) in that directory: git init -shared=all -bare /srv/git/lwip/lwip-contrib.git If a project wishes to have several repositories grouped together The git:// lightweight protocol is also available. Git+ssh is supported in Savane's sv_membersh (delegates to git-shell). Repositories are in /srv/git/project_name.git for now. User documentation: UsingGit Current setup
0 Comments
Leave a Reply. |