Re: [Wireshark-dev] [Wireshark-commits] rev 53619: /trunk/ /trunk/: NEWS

2013-11-28 Thread Martin Kaiser
Thus wrote Guy Harris (g...@alum.mit.edu):


 On Nov 27, 2013, at 3:09 PM, jma...@wireshark.org wrote:

  http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=53619

  User: jmayer
  Date: 2013/11/27 11:09 PM

  Log:
  Having a generated file in the source tree is not fun.

 Should we add a top-level rule to make it, and remove it from SVN?

+1

Last time I added a protocol and modified release-notes.asciidoc, I
couldn't figure out if/how I should update NEWS.
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


Re: [Wireshark-dev] [Wireshark-commits] rev 53619: /trunk/ /trunk/: NEWS

2013-11-28 Thread Joerg Mayer
On Thu, Nov 28, 2013 at 10:01:52AM +0100, Martin Kaiser wrote:
 Thus wrote Guy Harris (g...@alum.mit.edu):
 
 
  On Nov 27, 2013, at 3:09 PM, jma...@wireshark.org wrote:
 
   http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=53619
 
   User: jmayer
   Date: 2013/11/27 11:09 PM
 
   Log:
   Having a generated file in the source tree is not fun.
 
  Should we add a top-level rule to make it, and remove it from SVN?
 
 +1
 
 Last time I added a protocol and modified release-notes.asciidoc, I
 couldn't figure out if/how I should update NEWS.

cmake:
cd docbook
make release_notes

autotools:
cd docbook
make release_notes

OK, so they are identical. Main problem are the required tools, but
developers should be able to live with reading
docbook/release-notes.asciidoc instead of NEWS.

How about removing the NEWS file and just making sure that it is
generated for packaging?

Once that is done we can move to the asn1/ stuff - which should then be
moved to epan/dissectors/asn1/ ;-)

Ciao
 Jörg
-- 
Joerg Mayer   jma...@loplof.de
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] [Wireshark-commits] rev 53619: /trunk/ /trunk/: NEWS

2013-11-28 Thread Graham Bloice
On 28 November 2013 12:47, Joerg Mayer jma...@loplof.de wrote:


 Once that is done we can move to the asn1/ stuff - which should then be
 moved to epan/dissectors/asn1/ ;-)



Not so fast, we need to get Windows CMake done first :-)
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe