Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
vlc-1.1
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Redmine
Redmine
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Metrics
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
videolan
vlc-1.1
Commits
1292f91e
Commit
1292f91e
authored
Jan 24, 2003
by
Sam Hocevar
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
* ./doc/bugreport-howto.txt: minor updates.
parent
4bbe6f6f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
4 deletions
+7
-4
doc/bugreport-howto.txt
doc/bugreport-howto.txt
+7
-4
No files found.
doc/bugreport-howto.txt
View file @
1292f91e
...
@@ -51,8 +51,11 @@
...
@@ -51,8 +51,11 @@
* Where to send bug reports?
* Where to send bug reports?
- The vlc-devel mailing-list is probably the best place to send your
- Use the Bugzilla interface at http://bugzilla.videolan.org/. If you
bug report, just email it to <vlc-devel@videolan.org>. If you are
do not want to leave your email address, just use "guest" as both the
concerned by the size of the attached files, you can put them on a
username and password. You will not be notified about the evolution of
website and post their address instead.
your bug though.
- The vlc-devel mailing-list is also a good place to discuss issues
with all developers, but bug reports are better sent to Bugzilla.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment