2
votes
1answer
52 views
“Files” tab lacks support for branches
The "Files" tab currently has a drop-down with tag names, but lacks support for branches. Actually, you can just enter a branch name and it will work (selects the branch head).
So …
9
votes
2answers
215 views
Code review support for named branches
We've been using named branches to implement the branch-per-feature pattern and have found that it seems to work really well with Kiln overall. The one thing we're having trouble m …
17
votes
3answers
7k views
Why are branched repositories preferred over named branches in Mercurial?
I am new to mercurial and I am trying to grok the whole branched repository vs. named branch issue.
It seems that the mercurial dev team and most of the experienced users have s …
1
vote
1answer
128 views
why not use branches?
Hi,
going through the tutorial at hginit.com I understand that you recommend to clone the project repository to isolate feature development. see http://hginit.com/05.html
On the …
0
votes
2answers
489 views
Best practice to maintain different build configs for the same code
Background: This pertains specifically to building DLLs to extend AutoCAD. Every 3 years they change the binary compatibility, generally also changing the version of the .NET frame …
3
votes
2answers
162 views
Feature Request: Access to Kiln repository hgrc
Some extensions (e.g. the acl extension) require access to the repository's .hg/hgrc file in order to be configured. It would be incredibly helpful to have some kind of access to t …
2
votes
1answer
442 views
Remove “Trunk” named branch?
When importing a repository from SVN, how do I remove the "Trunk" named branch that shows up in both TortoiseHG and Kiln?
I have tried using both Kiln Importer and running hg --co …
2
votes
3answers
581 views
Does it make sense to use named branches and branch repositories together?
First off, I like most of what branch repositories offer. They're easier to manage from Kiln. They're easier to throw away if needed. They're easier to work with in most ways. …
3
votes
1answer
463 views
“Fog Creek recommends using Kiln branches” and TortoiseHG 2.0
When you release TortoiseHG 2.0, will you be disabling the nobranch.py warning?
If you attempt to commit on a named branch, the following happens:
% hg branch --repository C:\ine …
2
votes
1answer
120 views
Add review final version of file for reviews with multiple changesets [closed]
Possible Duplicate:
create code review from kiln file view?
When a review contains multiple changesets and using the "by files" mode, individual files are listed for diffe …
1
vote
1answer
119 views
“All Heads” list should not show heads from closed named branches
In an older question that I asked, there was some discussion around the fact that the "all heads" feature includes heads from closed named branches. Now that my company has been us …
2
votes
2answers
525 views
Named branches issue
Ok I know there's lots of controversy surrounding named branches, whether to use them or not, blah blah blah.
I'm coming from git, so named branches seem to me to be a bit like gi …
3
votes
2answers
124 views
Feature Request: Add support for ACL extension
We'd like to see support for the acl extension for use with a central or branch repository.
There are a couple of use cases for this request:
Access control over named branches. …
6
votes
2answers
179 views
Feature request: Submit a code review for all changes in a named branch
We are using the named-branch-per-feature model, and it's working really well. Creating reviews is usually not a problem when a branch has one or a few commits over a short period …
5
votes
3answers
2k views
Selectively converting SVN branches
I'm playing around with the best way to import our existing 3-year-old Subversion repository to Kiln.
We have several branches that are essentially dead, and I would prefer not to …